I'm setting up a chain of projects, where when Project A finishes building, 
I invoke Project B using the "build" command.  However, the build command 
always sync's to whatever HEAD is currently set to on the remote.  My 
Jenkinsfile, later syncs to the hash I want.  However, at this point the 
change log is already polluted.

I.e. in Project B I want to build at hash X, however, at spin up Project B 
clones to hash Y, where Y is newer than X.  All the changes between X and Y 
are now part of the change log.

Any way to get around this?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/952355a3-e715-49d1-8398-3b2776d917ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to