We are migrating from a single build pipeline to a pair of pipelines. The
first will build our "platform" and then the second will build the
application. This is because we will soon have multiple applications using
the same platform.
The applications should build if the platform changes OR
OK, so this isn't going so hot. There is no .m2/settings.xml file. There
are settings.xml for each of the Maven versions under
~/tools/hudson.tasks.Maven_MavenInstallation/Maven-X.X/conf. This has the
"localRepository" node but it's commented out. Should I set the value
Thanks, deleted it for short term solution and looking into the "Even
Better" solution at your link. Much appreciated!
On Friday, December 17, 2021 at 4:12:50 AM UTC-7 bma...@gmail.com wrote:
> Yeah you can definitely wipe out this whole tree.
>
> I wrote an eternity ago about this:
>
>
>
Hi Adharsha,
We don’t use freestyle, so I may not be the best person to help you.
I’m struggling although to understand the logic you want to implement.
You said that in the “second job” configuration you configured “build trigger”
and selected “first job”.
But then you said you click “Build
Hi,
We created 2 freestyle jobs( first job, second job) and we have mentioned
first job in *build trigger - build after other projects are build( if
build is stable) * in second job configuration. When we click buildnow in
second job , it need to trigger first job and if it is
successfully
Hi Adharsha,
We use this in our pipeline and works:
def job = build([
job: “Job/name”,
wait: true,
propagate: false
])
What are the errors that you are experience on doing it?
Can you add more details?
Cheers,
Gianluca.
From: jenkinsci-users@googlegroups.com On
Hi Team,
Need to trigger the upstream job from the run downstream job.
We are able to trigger the down stream job from upstream job but not in
reverse direction. Can you please help us.
Requirement:
First job <-- Second job
When I run second job it should trigger upstreamjob (I.e. first
Yeah you can definitely wipe out this whole tree.
I wrote an eternity ago about this:
https://batmat.net/2009/10/09/hudson-how-to-set-a-private-maven-repository-by-job-and-easily-be-able-to-delete-them/
Some of it is a bit old but the principles remain true today: you _should_
even do it on a
