Mixing
How to test outcome of git pull?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I would like to test the outcome of git pull.
Currently we use this deployment approach:
git pull && rake build && rake deploy
However it unfortunately does much unnecessary work in the case that the pull is a no-op.
Can this be improved?
git zsh
asked Jan 3 at 16:30
William EntrikenWilliam Entriken
20.6k1093144
|
show 5 more comments
I would like to test the outcome of git pull.
Currently we use this deployment approach:
git pull && rake build && rake deploy
However it unfortunately does much unnecessary work in the case that the pull is a no-op.
Can this be improved?
git zsh
asked Jan 3 at 16:30
William EntrikenWilliam Entriken
20.6k1093144
Can you add some detail describing what result you want? What do you mean by pull being a no-op? Ifgit pulldetermines that the current branch is up to date, then it will still succeed and return 0 because no error occurred.
– Code-Apprentice
Jan 3 at 16:34
Searching docs now, But My thought is thatgit pullis actuallygit fetch && git merge. Maybe do agit fetchthen compare branchesmasterandorigin/master
– Philip Couling
Jan 3 at 16:36
@Code-Apprentice The OP wants to find out if anything will / has changed after agit pull.
– Philip Couling
Jan 3 at 16:36
@PhilipCouling That is my working assumption as well. However, until the OP clarifies, we are only guessing.
– Code-Apprentice
Jan 3 at 16:38
What is usually done for deployment jobs using a CI tool is connecting to the repository and triggering the job just in case of change in the repo.
– Matt
Jan 3 at 16:39
|
show 5 more comments
I would like to test the outcome of git pull.
Currently we use this deployment approach:
git pull && rake build && rake deploy
However it unfortunately does much unnecessary work in the case that the pull is a no-op.
Can this be improved?
git zsh
asked Jan 3 at 16:30
William EntrikenWilliam Entriken
20.6k1093144
I would like to test the outcome of git pull.
Currently we use this deployment approach:
git pull && rake build && rake deploy
However it unfortunately does much unnecessary work in the case that the pull is a no-op.
Can this be improved?
git zsh
git zsh
asked Jan 3 at 16:30
William EntrikenWilliam Entriken
20.6k1093144
asked Jan 3 at 16:30
William EntrikenWilliam Entriken
20.6k1093144
edited Jan 3 at 17:12
William Entriken
asked Jan 3 at 16:30
William EntrikenWilliam Entriken
20.6k1093144
asked Jan 3 at 16:30
William EntrikenWilliam Entriken
20.6k1093144
asked Jan 3 at 16:30
William EntrikenWilliam Entriken
20.6k1093144
20.6k1093144
Can you add some detail describing what result you want? What do you mean by pull being a no-op? Ifgit pulldetermines that the current branch is up to date, then it will still succeed and return 0 because no error occurred.
– Code-Apprentice
Jan 3 at 16:34
Searching docs now, But My thought is thatgit pullis actuallygit fetch && git merge. Maybe do agit fetchthen compare branchesmasterandorigin/master
– Philip Couling
Jan 3 at 16:36
@Code-Apprentice The OP wants to find out if anything will / has changed after agit pull.
– Philip Couling
Jan 3 at 16:36
@PhilipCouling That is my working assumption as well. However, until the OP clarifies, we are only guessing.
– Code-Apprentice
Jan 3 at 16:38
What is usually done for deployment jobs using a CI tool is connecting to the repository and triggering the job just in case of change in the repo.
– Matt
Jan 3 at 16:39
|
show 5 more comments
Can you add some detail describing what result you want? What do you mean by pull being a no-op? Ifgit pulldetermines that the current branch is up to date, then it will still succeed and return 0 because no error occurred.
– Code-Apprentice
Jan 3 at 16:34
Searching docs now, But My thought is thatgit pullis actuallygit fetch && git merge. Maybe do agit fetchthen compare branchesmasterandorigin/master
– Philip Couling
Jan 3 at 16:36
@Code-Apprentice The OP wants to find out if anything will / has changed after agit pull.
– Philip Couling
Jan 3 at 16:36
@PhilipCouling That is my working assumption as well. However, until the OP clarifies, we are only guessing.
– Code-Apprentice
Jan 3 at 16:38
What is usually done for deployment jobs using a CI tool is connecting to the repository and triggering the job just in case of change in the repo.
– Matt
Jan 3 at 16:39
Can you add some detail describing what result you want? What do you mean by pull being a no-op? If
git pull determines that the current branch is up to date, then it will still succeed and return 0 because no error occurred.– Code-Apprentice
Jan 3 at 16:34
Can you add some detail describing what result you want? What do you mean by pull being a no-op? If
git pull determines that the current branch is up to date, then it will still succeed and return 0 because no error occurred.– Code-Apprentice
Jan 3 at 16:34
Searching docs now, But My thought is that
git pull is actually git fetch && git merge. Maybe do a git fetch then compare branches master and origin/master– Philip Couling
Jan 3 at 16:36
Searching docs now, But My thought is that
git pull is actually git fetch && git merge. Maybe do a git fetch then compare branches master and origin/master– Philip Couling
Jan 3 at 16:36
@Code-Apprentice The OP wants to find out if anything will / has changed after a
git pull.– Philip Couling
Jan 3 at 16:36
@Code-Apprentice The OP wants to find out if anything will / has changed after a
git pull.– Philip Couling
Jan 3 at 16:36
@PhilipCouling That is my working assumption as well. However, until the OP clarifies, we are only guessing.
– Code-Apprentice
Jan 3 at 16:38
@PhilipCouling That is my working assumption as well. However, until the OP clarifies, we are only guessing.
– Code-Apprentice
Jan 3 at 16:38
What is usually done for deployment jobs using a CI tool is connecting to the repository and triggering the job just in case of change in the repo.
– Matt
Jan 3 at 16:39
What is usually done for deployment jobs using a CI tool is connecting to the repository and triggering the job just in case of change in the repo.
– Matt
Jan 3 at 16:39
|
show 5 more comments
2 Answers
2
active
oldest
votes
There's basically two things you can do. You can interpret the output, or you can interrogate to see if anything has changed.
You haven't specified your shell (windows or a unix shell like bash) so I can't give example code. But git pull will print Already up-to-date. if nothing changes. So skip the build and deploy if that happens.
The second option is to check your commit number before and after using:
git rev-list -n 1 HEAD
If this changes, then the pull did something, if not then it didn't
answered Jan 3 at 16:47
Philip CoulingPhilip Couling
7,4002553
Thank you, good idea. So now we usegit pull|grep -v Already&&rake build deploy
– William Entriken
Jan 3 at 17:16
add a comment |
Use git log -1 --pretty=format:%H to get the commit hash before and after the git pull.
Compare both hashes and start a build when they differ.
answered Jan 3 at 16:46
Roland SmithRoland Smith
27.1k33257
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54026241%2fhow-to-test-outcome-of-git-pull%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
There's basically two things you can do. You can interpret the output, or you can interrogate to see if anything has changed.
You haven't specified your shell (windows or a unix shell like bash) so I can't give example code. But git pull will print Already up-to-date. if nothing changes. So skip the build and deploy if that happens.
The second option is to check your commit number before and after using:
git rev-list -n 1 HEAD
If this changes, then the pull did something, if not then it didn't
answered Jan 3 at 16:47
Philip CoulingPhilip Couling
7,4002553
Thank you, good idea. So now we usegit pull|grep -v Already&&rake build deploy
– William Entriken
Jan 3 at 17:16
add a comment |
There's basically two things you can do. You can interpret the output, or you can interrogate to see if anything has changed.
You haven't specified your shell (windows or a unix shell like bash) so I can't give example code. But git pull will print Already up-to-date. if nothing changes. So skip the build and deploy if that happens.
The second option is to check your commit number before and after using:
git rev-list -n 1 HEAD
If this changes, then the pull did something, if not then it didn't
answered Jan 3 at 16:47
Philip CoulingPhilip Couling
7,4002553
Thank you, good idea. So now we usegit pull|grep -v Already&&rake build deploy
– William Entriken
Jan 3 at 17:16
add a comment |
There's basically two things you can do. You can interpret the output, or you can interrogate to see if anything has changed.
You haven't specified your shell (windows or a unix shell like bash) so I can't give example code. But git pull will print Already up-to-date. if nothing changes. So skip the build and deploy if that happens.
The second option is to check your commit number before and after using:
git rev-list -n 1 HEAD
If this changes, then the pull did something, if not then it didn't
answered Jan 3 at 16:47
Philip CoulingPhilip Couling
7,4002553
There's basically two things you can do. You can interpret the output, or you can interrogate to see if anything has changed.
You haven't specified your shell (windows or a unix shell like bash) so I can't give example code. But git pull will print Already up-to-date. if nothing changes. So skip the build and deploy if that happens.
The second option is to check your commit number before and after using:
git rev-list -n 1 HEAD
If this changes, then the pull did something, if not then it didn't
answered Jan 3 at 16:47
Philip CoulingPhilip Couling
7,4002553
answered Jan 3 at 16:47
Philip CoulingPhilip Couling
7,4002553
answered Jan 3 at 16:47
Philip CoulingPhilip Couling
7,4002553
answered Jan 3 at 16:47
Philip CoulingPhilip Couling
7,4002553
7,4002553
Thank you, good idea. So now we usegit pull|grep -v Already&&rake build deploy
– William Entriken
Jan 3 at 17:16
add a comment |
Thank you, good idea. So now we usegit pull|grep -v Already&&rake build deploy
– William Entriken
Jan 3 at 17:16
Thank you, good idea. So now we use
git pull|grep -v Already&&rake build deploy– William Entriken
Jan 3 at 17:16
Thank you, good idea. So now we use
git pull|grep -v Already&&rake build deploy– William Entriken
Jan 3 at 17:16
add a comment |
Use git log -1 --pretty=format:%H to get the commit hash before and after the git pull.
Compare both hashes and start a build when they differ.
answered Jan 3 at 16:46
Roland SmithRoland Smith
27.1k33257
add a comment |
Use git log -1 --pretty=format:%H to get the commit hash before and after the git pull.
Compare both hashes and start a build when they differ.
answered Jan 3 at 16:46
Roland SmithRoland Smith
27.1k33257
add a comment |
Use git log -1 --pretty=format:%H to get the commit hash before and after the git pull.
Compare both hashes and start a build when they differ.
answered Jan 3 at 16:46
Roland SmithRoland Smith
27.1k33257
Use git log -1 --pretty=format:%H to get the commit hash before and after the git pull.
Compare both hashes and start a build when they differ.
answered Jan 3 at 16:46
Roland SmithRoland Smith
27.1k33257
answered Jan 3 at 16:46
Roland SmithRoland Smith
27.1k33257
answered Jan 3 at 16:46
Roland SmithRoland Smith
27.1k33257
answered Jan 3 at 16:46
Roland SmithRoland Smith
27.1k33257
27.1k33257
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54026241%2fhow-to-test-outcome-of-git-pull%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Can you add some detail describing what result you want? What do you mean by pull being a no-op? If
git pulldetermines that the current branch is up to date, then it will still succeed and return 0 because no error occurred.– Code-Apprentice
Jan 3 at 16:34
Searching docs now, But My thought is that
git pullis actuallygit fetch && git merge. Maybe do agit fetchthen compare branchesmasterandorigin/master– Philip Couling
Jan 3 at 16:36
@Code-Apprentice The OP wants to find out if anything will / has changed after a
git pull.– Philip Couling
Jan 3 at 16:36
@PhilipCouling That is my working assumption as well. However, until the OP clarifies, we are only guessing.
– Code-Apprentice
Jan 3 at 16:38
What is usually done for deployment jobs using a CI tool is connecting to the repository and triggering the job just in case of change in the repo.
– Matt
Jan 3 at 16:39