Yes, but there is a problem. In the build information I think it will
display the sha1 of the branch checked out automatically rather than that
of the specific commit that I checkout by hand (at least this is what I
though I have seen while I was testing a similar approach ;) ).
But thanks!
On Fr
Hi,
you could install gerrit-trigger-plugin (you do not need to use gerrit for
your use-case) and use the gerrit-trigger checkout strategy that can
use hashes/tags/etc...
Björn
Am Mittwoch, 25. März 2015 15:26:37 UTC+1 schrieb Lóránt Pintér:
>
> Hi,
>
> Is it possible to check out a particula
I did, but to me it doesn't work, it checks out anyway the next branch... :(
On Fri, Mar 18, 2016 at 8:58 AM, Baptiste Mathus wrote:
> Did you try using the generic SCM way as proposed by Jesse?
> Le 17 mars 2016 4:51 PM, "Simone Vratogna" a écrit :
>
>> Hello, I'm interested as well. Did you f
Did you try using the generic SCM way as proposed by Jesse?
Le 17 mars 2016 4:51 PM, "Simone Vratogna" a écrit :
> Hello, I'm interested as well. Did you find any solution?
>
> On Wednesday, March 25, 2015 at 3:26:37 PM UTC+1, Lóránt Pintér wrote:
>>
>> Hi,
>>
>> Is it possible to check out a par
Hello, I'm interested as well. Did you find any solution?
On Wednesday, March 25, 2015 at 3:26:37 PM UTC+1, Lóránt Pintér wrote:
>
> Hi,
>
> Is it possible to check out a particular commit hash, instead of a branch
> with the git workflow step?
>
> Thanks,
> Lorant
>
--
You received this messag
Now thinking about it, another solution is to just use the plain git CLI.
(Requires git on the path, note)
*def theSha = ""*
*sh "git checkout $theSha"*
*// here you go*
2016-03-18 9:12 GMT+00:00 'Björn Pedersen' via Jenkins Users <
jenkinsci-users@googlegroups.com>:
> Hi,
>
> you could in
On Wednesday, June 17, 2015 at 2:53:25 PM UTC-4, Stephan Stachurski wrote:
>
> using our conventional jenkins pipeline, we have been burned in the past
> when the head of a branch changed between the start and end of the pipeline.
>
If using a multibranch workflow (currently in beta), you just sa
I would really like to figure this out. Haven't transitioned to workflow
yet, but using our conventional jenkins pipeline, we have been burned in
the past when the head of a branch changed between the start and end of the
pipeline.
On Tuesday, June 16, 2015 at 2:50:37 PM UTC-4, Jesse Glick wrot
On Wednesday, March 25, 2015 at 10:26:37 AM UTC-4, Lóránt Pintér wrote:
>
> Is it possible to check out a particular commit hash, instead of a branch
> with the git workflow step?
>
No, but it should be possible with some exotic options to GitSCM, run via
the generic checkout step.
--
You rec
I tried, but it results in weird errors about no commit being found to build:
Running: Git
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url g...@github.com:prezi/boxfish-text-editor.git #
timeout=10
Fetchin
Just a wild guess: since in Git branch names are actually not very special
things, which in the end get translated to the associated sha1, did you
just try to put branch: 'abc123' e.g. ?
2015-03-25 15:26 GMT+01:00 Lóránt Pintér :
> Hi,
>
> Is it possible to check out a particular commit hash, ins
11 matches
Mail list logo
