Setting up two organization folders was the trick. Thanks!
On Wednesday, December 13, 2017 at 2:29:19 PM UTC-8, Stephen Connolly wrote:
>
> Use a shared library to define the steps with a common name.
>
> Each branch will just have a Jenkinsfile of
>
> ourStandardBuild();
>
> Then you define two
>
> Do you know if all builds from each PR go to the same job that is created
> in the build-a-job step?
>
Yes, indeed. I don't know in your specific use case, but using concurrent
builds you can solve concurrent PR executions if you got enough agents too.
--
You received this message
Use a shared library to define the steps with a common name.
Each branch will just have a Jenkinsfile of
ourStandardBuild();
Then you define two org folders. One for the new build and the other for
the old build.
Add the respective shared library to each org folder.
See Watch Me Code Episodes
Thanks for the quick reply - that's an intriguing proposition!
Do you know if all builds from each PR go to the same job that is created
in the build-a-job step?
On Wednesday, December 13, 2017 at 2:10:45 PM UTC-8, Victor Martinez wrote:
>
> if the old tests will be deprecated and removed
if the old tests will be deprecated and removed sooner than later, cannot
you just use
the
https://jenkins.io/doc/pipeline/steps/pipeline-build-step/#build-build-a-job
step?
Then, the Jenkinsfile will trigger two parallel branches, the first one
about the new tests using whatever is part of
Hello! I am new to Jenkins, and would appreciate help with the following
scenario.
I have been tasked with migrating an existing testing framework to a new
one for my team's CI infrastructure. This resulted in the need for a
rewrite of our current, existing tests. As a result, we now have a
