Hi!
We call pipeline shared libraries in our Jenkinsfile via standard clause:
"@Library('pipeline-library') _" and noticed that github plugin
automatically activates webhooks for shared library repository as well as
for application one. We don't need to have webhook for shared library in
the a
Pipeline multibranch will get you half way there with the resolveScm step
(what's missing is triggering based on changes to the second repository)
On Sat 18 Mar 2017 at 19:31, Nishanth Prakash
wrote:
> I need to track only two branches. One of the branch it need to track is
> specified using SHA
Downstream jobs will run on any agent matching the label they are
configured for, with preference given to running on the agent that they
most recently ran on *if idle*.
Upstream jobs have no affect - unless they are still running at the time -
in which case they may force a *different* agent if t
I need to track only two branches. One of the branch it need to track is
specified using SHA value, if that is null it should default back to
master? Is there anyway to do that using SCM plugin?
Thanks
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users
Does this mean I am correct that the default behavior is for downstream
projects to run on any agents that have the same label ? This was perhaps
the big thing I was trying to find out.
Also our builds are done via "build job: " but I am struggling to find out
how to force it to use a particula
Dang! I thought that stuff was free. Oh well sorry... could have sworn...
On Sat 18 Mar 2017 at 17:21, Dan Tran wrote:
> hmm, looking further, I need 'Folder Plus' plugin. It is not free
>
>
> https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/index.html#folder
>
> Thanks
>
hmm, looking further, I need 'Folder Plus' plugin. It is not free
https://go.cloudbees.com/docs/cloudbees-documentation/cje-user-guide/index.html#folder
Thanks
-Dan
On Sat, Mar 18, 2017 at 10:15 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Are you sure?
>
> On Sat 18 Ma
Are you sure?
On Sat 18 Mar 2017 at 17:02, Dan Tran wrote:
> Unfortunately, there is no Jenkins capability to inject environment vars
> at folder level
>
> Thanks
>
> -Dan
>
>
> On Saturday, March 18, 2017 at 1:15:34 AM UTC-7, Stephen Connolly wrote:
>
> You could also define env vars at the fol
Unfortunately, there is no Jenkins capability to inject environment vars at
folder level
Thanks
-Dan
On Saturday, March 18, 2017 at 1:15:34 AM UTC-7, Stephen Connolly wrote:
>
> You could also define env vars at the folder level (as multibranch is a
> folder) and then use conditions based on t
I think you would need to write a plugin that enforces your "same node"
constraint.
It would not be general utility as eg enough people are doing builds on
ephemeral agents and you'd end up with stuck jobs waiting for a free
executor on the same "ephemeral" node that will never return.
But I can
Hi,
We have multiple pipelines for which each will run 3+ downstream freestyle
projects.
This process is defined by an automation tool that creates and initiates
Jenkins builds, so using other methodologies is out :-). The problem I have
is that I need all the freestyle projects to run on the
Hi all,
I'm testing out a pipeline build in Jenkins using the AWS EC2 plugin. Via
the plugin, a build will spin up an EC2 instance and run my init script,
which you will find detailed in the Gist below:
https://gist.github.com/bsodmike/7033ffeab2383599bb38a2bcf263aba4
The init script adds the
It seems to me, this issue is either a XVFB one or an environmental issue
rather than a plugin/jenkins issue. Worth trying some of the suggestions
from stack-overflow or any other reference pages
The below page might help you out:
-
http://unix.stackexchange.com/questions/232749/xvfb-screen-can
You could also define env vars at the folder level (as multibranch is a
folder) and then use conditions based on the env vars... less elegant I know
On Sat 18 Mar 2017 at 07:22, Dan Tran wrote:
> I have a requirement to run maven sonar:sonar against all branches. This
> means my Jenkinsfile must
I have a requirement to run maven sonar:sonar against all branches. This
means my Jenkinsfile must explicitly invoke sonar and can only run sonar
only environment
if jenkins pipline allows injection of a user env variable, my Jenkinsfile
can react appropriately.
However, I just found a promis
15 matches
Mail list logo