I have a github based multibranch project that uses pipeline libraries.
Triggering the scan of a repository (either manually or through a schedule)
rebuilds all open branches and pull requests if there has been a change
made to the pipeline code even if no change has happened on the main
reposi
I face the same issue with Mesos and my understanding is that there is a
way to declare slaves as *ephemeral* i.e.they will never come back once
they are gone. This appeared to be something that the cloud provider plugin
(mesos in this case) needs to worry about.
On Thursday, May 25, 2017 at 7
The environment variable CHANGE_ID contains the PR number
On Friday, May 26, 2017 at 6:07:20 AM UTC+5:30, Cody Ebberson wrote:
>
> Hello,
>
> I'm configuring Github + Jenkins + Sonar. Almost everything is working,
> and I am incredibly pleased (great job!) I'm now struggling with one
> missing
Is there a way to directly access the value of token macros such as
WARNINGS_FIXED, WARNINGS_COUNT from a non-declarative pipeline?
Also, will the solution work from within library functions or does this
have to be at the top level?
--
You received this message because you are subscribed to th
I'd like find out the following things from a multibranch pipeline script
associated with a github scm provider
- Is this build happening for a branch or a pull request?
- If it is for a pull request, then I need to know these as well
- Commit-id of the tip of pull request
- Com
Should I be raising this as a bug instead?
On Monday, December 12, 2016 at 9:38:37 PM UTC+5:30, Arvind Jayaprakash
wrote:
>
> Yes. I've attached the versions of all plugins as a reference
>
> On Monday, December 12, 2016 at 9:33:31 PM UTC+5:30, Daniel Beck wrote:
>>
>&
This might be unrelated, but I ran into the magic 60 minute barrier on AWS
when using an ELB. Connections over ELB that are idle for 60 minutes get
terminated. I'd check for similar settings on say your tomcat config, the
connection to your slave etc. etc.
On Tuesday, December 6, 2016 at 9:16:
Yes. I've attached the versions of all plugins as a reference
On Monday, December 12, 2016 at 9:33:31 PM UTC+5:30, Daniel Beck wrote:
>
>
> > On 12.12.2016, at 12:55, Arvind Jayaprakash > wrote:
> >
> > I guess this is not the first report on the build abort act
I guess this is not the first report on the build abort action not working
in a pipeline (based on past mails I see this group). I write to
demonstrate a full example where this doesn't work. Here is my pipeline in
it's entiry
node('mvn-3.3-jdk-8') {
stage('stoopid grep') {
sh 'grep aa -R
This plugin is letting me do everything I wanted.
https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Integration+Plugin
The plugin lets me trigger pipelines based on pull request triggers from
github without imposing any conventions on files that needs to be
present in the source trees.
I then ab
On Tuesday, August 16, 2016 at 12:17:44 AM UTC+5:30, Jesse Glick wrote:
>
> On Sunday, August 14, 2016 at 1:28:50 AM UTC-4, Arvind Jayaprakash wrote:
>>
>> A world wherein the following can happen is god enough
>>>
>>
>>- "jenkins team"
:02:07 PM UTC+5:30, Arvind Jayaprakash
wrote:
>
> I seem to have developed a love/hate relationship with Jenkins 2.x
> pipelines and some of the concepts that it imposes. Hence, I'd like to hear
> how best operate in the new world. The one thing I'd like to make clear
> b
eam" to ensure that the latest pipeline
libraries are being used
> Mark Waite
>
> On Sat, Aug 13, 2016 at 9:32 AM Arvind Jayaprakash > wrote:
>
>> I seem to have developed a love/hate relationship with Jenkins 2.x
>> pipelines and some of the concepts
I seem to have developed a love/hate relationship with Jenkins 2.x
pipelines and some of the concepts that it imposes. Hence, I'd like to hear
how best operate in the new world. The one thing I'd like to make clear
before I get into the details is that I am suggesting that this the only
right w
14 matches
Mail list logo
