Ben Parees
Ben Parees
> later on the build was treated as binary deployment and my image tries to find JAR instead of cloning a Git repo and build the code. hmm, i'd have...
@mjudeikis very related to the PR you were already working related to not doing source detection when a builder image is provided.
@mjudeikis I think those look fine for expected behaviors. I could quibble with (5) (it's possible we should error in that case and force you to use the ~ syntax)...
I'm in favor of this since we should be the only ones writing to status and we've already been through at least one painful revert as a result of this...
> @bparees Are there any requirements for having directory for each version? there are no requirements, since you guys own the CI/CD infrastructure and getting the images built on OSBS,...
this is insufficient information for us to help you. Please provide: 1) the error you are seeing 2) the steps required to reproduce your error 3) any additional relevant details...
are you suggesting the readme be updated to reflect the new syntax? or is there somewhere else that needs to be changed? i'd be happy to merge a PR to...
@xiuwang does this need to remain open forever? If so, it might be better for QE to create a fork of the repo and put the PR there.
This just started happening in our jenkins as well. not sure if anything (plugin or jenkins itself) was updated when it happened, but it seems like no.