Re: How to set Multibranch Pipeline Trigger interval via Jenkinsfile?

[Ramanathan Muthaiah]

On Thursday, July 27, 2017 at 5:12:55 AM UTC+5:30, Yuri Govorushchenko 
wrote:
>
> Hello,
>
> I have a *Multibranch Pipeline* job and would like to programatically set 
> its property found in UI at *Scan Multibranch Pipeline Triggers -> 
> Periodically if not otherwise run -> Interval*. Ideally I'd like to do it 
> in a scripted *Jenkinsfile* used to define the job. Maybe it can be 
> somehow achieved via properties step? It seems to be a property of 
> CloudBees Folders Plugin 
>  but I 
> couldn't figure out how it can be modified without a UI.
>

We are on the same boat . . . would be interested to know how this can be 
done; if you hit upon the solution, pls do share here.

/Ram 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/ace70cd8-afa6-4966-a82c-e449cad3eeef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to set Multibranch Pipeline Trigger interval via Jenkinsfile?

[Yuri Govorushchenko]

Hello,

I have a *Multibranch Pipeline* job and would like to programatically set 
its property found in UI at *Scan Multibranch Pipeline Triggers -> 
Periodically if not otherwise run -> Interval*. Ideally I'd like to do it 
in a scripted *Jenkinsfile* used to define the job. Maybe it can be somehow 
achieved via properties step? It seems to be a property of 
CloudBees Folders Plugin 
 but I 
couldn't figure out how it can be modified without a UI.

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d5304260-8e49-4ad1-b302-9b8b685973cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to get access to a Maven POM version in a Freestyle build?

[Eric B]

Due to my project structure, and the desire to use the .mvn/maven.config 
configuration file to specify my default maven configuration, I have 
created my build definition as a Freestyle project.

The build runs successfully, however I would like to include the version 
number in a tag in a post-build step.  Unfortunately, the maven POM_VERSION 
variable(s) are not accessible in a Freestyle project (only in a Maven 
build project).  Is there some other way I can extract the Version value 
from the pom.xml file?

I found a link in StackOverflow 
(https://stackoverflow.com/a/15879521/827480) executing a system groovy 
script but it was from 2013, and does not seem to export the POM_VERSION 
value as an environment variable in Jenkins 2.46+.  Additionally, from my 
understanding, this kind of workaround would only execute on a master node, 
which may be problematic.

import jenkins.util.*;
import jenkins.model.*;

def thr = Thread.currentThread();
def currentBuild = thr?.executable;
def workspace = currentBuild.getModuleRoot().absolutize().toString();

def project = new XmlSlurper().parse(new File("$workspace/pom.xml"))

def param = new hudson.model.StringParameterValue("POM_VERSION", 
project.version.toString())
currentBuild.addAction(new hudson.model.ParametersAction(param));



Is there another (ie: better) way to extract the version number from the 
pom file in a freestyle build?

Thanks,

Eric

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1f59886a-149c-4b21-b940-0b2b83b9ba0c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backing up JENKINS_HOME directory: files to exclude

[Victor Martinez]

OOI, have you tried 
https://wiki.jenkins.io/display/JENKINS/SCM+Sync+configuration+plugin ?

Cheers

On Wednesday, 26 July 2017 13:50:36 UTC+1, J0991 wrote:
>
> Hello Jenkins Community! 
>
> I currently have a Jenkins job which copies my JENKINS_HOME directory to 
> another directory, tars the copied directory, and then commits the 
> directory 
> to source control (Git, Bitbucket). 
>
> As far as best practices go, what files within JENKINS_HOME directory 
> should 
> be excluded from the copy before committing to source control? The tarred 
> copy of the directory resides in a Bitbucket repository which many users 
> have access to, and I'd like to prevent our Bitbucket users from accessing 
> sensitive files that reside in the JENKINS_HOME directory. 
>
> From the  Jenkins Wiki 
>    I was 
> able 
> to find the following information pertaining to backups: 
>
> *Back up and restore* 
> All the settings, build logs, artifact archives are stored under the 
> JENKINS_HOME directory. Simply archive this directory to make a back up. 
> Similarly, restoring the data is just replacing the contents of the 
> JENKINS_HOME directory from a back up. 
> Back ups can be taken without stopping the server, but when you restore, 
> please do stop the server. 
>
> It doesn't mention much as far as what files are unnecessary to backup or 
> what files should be excluded for security reasons. Thanks in advance for 
> any advice anyone may have! 
>
> - Jason 
>
>
>
> -- 
> View this message in context: 
> http://jenkins-ci.361315.n4.nabble.com/Backing-up-JENKINS-HOME-directory-files-to-exclude-tp4900826.html
>  
> Sent from the Jenkins users mailing list archive at Nabble.com. 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/79517e96-37a7-4515-9da4-29ce689af04f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Setup Declarative Script currentBuild.ChangeSets

[Joe Cavanaugh]

I've used a modified version of the scripts found on 
https://support.cloudbees.com/hc/en-us/articles/217630098-How-to-access-Changelogs-in-a-Pipeline-Job-
 
to great success by putting them as @NonCPS on the bottom of my declarative 
pipeline. Just recently I have moved the script to a global library that is 
now referenced in each corresponding job.

On Wednesday, July 26, 2017 at 10:56:01 AM UTC-5, Joaquin Henriquez wrote:
>
> Hi Guys
>
>  
>
> Does somebody has an example on the currentBuild.ChangeSets?
>
> Jenkins 2.60.2
>
>  
>
> On the Jelly emailext template (seems on the forEach changeSet.logs there 
> is nothing).
>
> Do I need to put anything on the declarative script before? On my file it 
> is under post,success
>
>  
>
> 
>
> 
>
>   
>
>   
>
> 
>
> 
>
>   Changes
>
> 
>
> 
>
>   
>
>   ${cs.msgAnnotated}
>
>   by ${cs.author}
>
>   
>
> 
>
>   
>
> ${spc}${p.editType.name}
>
> 
>
>   ${p.path}
>
> 
>
>   
>
> 
>
>   
>
> 
>
> 
>
>   No Changes
>
> 
>
> 
>
>   
>
> 
>
>  
>
>  
>
> 
> *Changes * 
>
>  
>
> No Changes
>
>  
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/53a9a81a-e8d3-4fc9-825e-80ad2f083db6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Setup Declarative Script currentBuild.ChangeSets

[Slide]

getChangeSets (build.changeSets) returns a list of
hudson.scm.ChangeLogSet, which
means you need an inner loop to iterate over each entry of each
ChangeLogSet.

On Wed, Jul 26, 2017 at 8:55 AM Joaquin Henriquez <
joaquin.henriq...@countercept.com> wrote:

> Hi Guys
>
>
>
> Does somebody has an example on the currentBuild.ChangeSets?
>
> Jenkins 2.60.2
>
>
>
> On the Jelly emailext template (seems on the forEach changeSet.logs there
> is nothing).
>
> Do I need to put anything on the declarative script before? On my file it
> is under post,success
>
>
>
> 
>
> 
>
>   
>
>   
>
> 
>
> 
>
>   Changes
>
> 
>
> 
>
>   
>
>   ${cs.msgAnnotated}
>
>   by ${cs.author}
>
>   
>
> 
>
>   
>
> ${spc}${p.editType.name}
>
> 
>
>   ${p.path}
>
> 
>
>   
>
> 
>
>   
>
> 
>
> 
>
>   No Changes
>
> 
>
> 
>
>   
>
> 
>
>
>
>
>
> 
> *Changes *
>
>
>
> No Changes
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/67680dbae74547958c3aac472cca59a7%40BSKEXCH2013HYPV.mwrinfosecurity.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVe4W0woQQL4Kt4RSFAwTnJjZSO%3DHoOjxJ9GW%3DV7uaNRuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Setup Declarative Script currentBuild.ChangeSets

[Joaquin Henriquez]

Hi Guys

Does somebody has an example on the currentBuild.ChangeSets?
Jenkins 2.60.2

On the Jelly emailext template (seems on the forEach changeSet.logs there is 
nothing).
Do I need to put anything on the declarative script before? On my file it is 
under post,success



  
  


  Changes


  
  ${cs.msgAnnotated}
  by ${cs.author}
  

  
${spc}${p.editType.name}

  ${p.path}

  

  


  No Changes


  




Changes


No Changes


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/67680dbae74547958c3aac472cca59a7%40BSKEXCH2013HYPV.mwrinfosecurity.com.
For more options, visit https://groups.google.com/d/optout.

Re: Delaying BitBucket Branch Source Plugin, but upgrade the rest

[Stephen Connolly]

yes, should be safe

the warning is because the data file format changes in 2.2.x and hence if
you upgrade you will be unable to downgrade safely without the assistance
of a backup of your job configuration

On 26 July 2017 at 06:02, Dan Tran  wrote:

>
> Due to an issue at https://github.com/topicusfinan/bitbucket-
> webhooks-plugin/issues/50, i have to delay the upgrade until that issue
> if fix.
>
> is it safe to upgrade its dependencies first?
>
> Thanks
>
> -Dan
>
> PS: my jenkins plugin update screen also display this
>
>
>
> Bitbucket Branch Source Plugin
> 
> Discover and build Bitbucket Cloud and Bitbucket Server pull requests and
> branches and send status notifications with the build result.
> Warning: This plugin requires dependent plugins be upgraded and at least
> one of these dependent plugins claims to use a different settings format
> than the installed version. Jobs using that plugin may need to be
> reconfigured, and/or you may not be able to cleanly revert to the prior
> version without manually restoring old settings. Consult the plugin release
> notes for details.
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/09c453c6-7da5-4ebd-b5ba-1eeb977fa2d1%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMyF3kziuWRXx-E-pdvg0QiRrX7D28b8L6e04iQZJJxoog%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Delaying BitBucket Branch Source Plugin, but upgrade the rest

[Dan Tran]

Due to an issue at 
https://github.com/topicusfinan/bitbucket-webhooks-plugin/issues/50, i have 
to delay the upgrade until that issue if fix.  

is it safe to upgrade its dependencies first?

Thanks

-Dan

PS: my jenkins plugin update screen also display this



Bitbucket Branch Source Plugin 

Discover and build Bitbucket Cloud and Bitbucket Server pull requests and 
branches and send status notifications with the build result.
Warning: This plugin requires dependent plugins be upgraded and at least 
one of these dependent plugins claims to use a different settings format 
than the installed version. Jobs using that plugin may need to be 
reconfigured, and/or you may not be able to cleanly revert to the prior 
version without manually restoring old settings. Consult the plugin release 
notes for details.




-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/09c453c6-7da5-4ebd-b5ba-1eeb977fa2d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Backing up JENKINS_HOME directory: files to exclude

[J0991]

Hello Jenkins Community!

I currently have a Jenkins job which copies my JENKINS_HOME directory to
another directory, tars the copied directory, and then commits the directory
to source control (Git, Bitbucket).

As far as best practices go, what files within JENKINS_HOME directory should
be excluded from the copy before committing to source control? The tarred
copy of the directory resides in a Bitbucket repository which many users
have access to, and I'd like to prevent our Bitbucket users from accessing
sensitive files that reside in the JENKINS_HOME directory.

>From the  Jenkins Wiki
   I was able
to find the following information pertaining to backups:

*Back up and restore*
All the settings, build logs, artifact archives are stored under the
JENKINS_HOME directory. Simply archive this directory to make a back up.
Similarly, restoring the data is just replacing the contents of the
JENKINS_HOME directory from a back up.
Back ups can be taken without stopping the server, but when you restore,
please do stop the server.

It doesn't mention much as far as what files are unnecessary to backup or
what files should be excluded for security reasons. Thanks in advance for
any advice anyone may have!

- Jason



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Backing-up-JENKINS-HOME-directory-files-to-exclude-tp4900826.html
Sent from the Jenkins users mailing list archive at Nabble.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1501073422887-4900826.post%40n4.nabble.com.
For more options, visit https://groups.google.com/d/optout.

Run Build Step on SVN modified files

[Jeff Stewart]

I'm having difficulties trying to reference the checked out files in a 
build step. I can get the workspace using that environment variable but I 
want to run a build step only on those files that are "new."

Example:
Jenkins run SVN Update

trunk\images\507959212.jpg is created in workspace

Run build step (windows batch command) on this new image


There may be other images in the workspace but I only want to run the build 
step on any new ones.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/67658ac5-40ae-4e08-96ad-b12bd0368f4f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: Stuck declarative script

[David Aldrich]

Fixed now. Needed to resume.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3405a1197164495d951f1fc33f2c7802%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.

[RFC] Static analysis plug-ins in pipelines

[Ullrich Hafner]

Im currently discussing with several users on how to improve the static 
analysis plug-ins for pipelines, see [1] for details.
If you are also using these plugins in your pipelines, feel free to leave any 
additional comments.

Ulli

[1] https://wiki.jenkins.io/display/JENKINS/Static+Analysis+in+Pipelines?cache

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/B10AFB80-838D-4A57-8429-E61C6816CD9C%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Message signed with OpenPGP

RE: Stuck declarative script

[David Aldrich]

The job's log states:

Waiting to resume part of MyJob_sw_builds » trunk #554: ???
Still paused

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/dc20762f10234733a10fbedcf47e1f77%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.

Pipeline property for GitHub PullRequest

[Ramanathan Muthaiah]

While regular GitHub PUSH event can be handled via this property setting in 
Jenkinsfile pipeline script, am interested to know if there is similar 
property for GitHub Pull Requests?

>>> pipelineTriggers([githubPush()])

Setup: 

Jenkins ver is @ 2.60.1, have webhook setup between GitHub Enterprise and 
Jenkins master.

Project is setup to trigger automatic build upon GitHub events (Push, PR), 
it is a regular pipeline job -- with regular Push event from GitHub, 
automatically fresh build job is triggered in the above setup, want to know 
if there is a similar way to handle PRs too via properties?

NOTE:
Am aware of other options that can be chosen while setting up project, 
like, GitHub organizational folder, MultiBranch Pipeline ; but, wanted to 
explore this PR topic with simple pipeline project setup in Jenkins.

/Ram

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/11e5398d-ece5-457e-8960-3a97337891db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins-jira-plugin: Failed to authenticate with JIRA

[James Green]

The Wiki page says:

"Starting from this plugin version 2.0, it is using JIRA REST API to
communicate instead of JIRA RPC SOAP which has been deprecated and removed
since JIRA v.7.0"

So that's the SOAP interface dropped since version 2. Inside JIRA I think
it's had a REST interface since around version 4. There's no suggestion
that the plugin should not work against the REST interface in JIRA-6.

My copy of IntelliJ is working against our JIRA-6 instance via the Tasks
component without trouble - which I strongly suspect is also using the REST
interface.

James


On 25 July 2017 at 13:48, Alex Johnson  wrote:

> Hello James,
>
> Glancing at the plugin wiki page
>  it seems you are
> correct - you need Jira v7.0 to use the latest version of the plugin.
>
> Installing version 1.41 (latest pre-2.0) could resolve this problem
> http://updates.jenkins-ci.org/download/plugins/jira/
> , but
> I'd suggest upgrading Jira to 7.0 if possible to use the latest version of
> the plugin.
>
> br,
> -Alex
>
> On Monday, July 24, 2017 at 4:02:42 AM UTC-4, James Green wrote:
>>
>> Got the latest LTS version of Jenkins with current jenkins-jira-plugin
>> and a JIRA 6.4 installation.
>>
>> I can log in to JIRA without issue and in the configuration I can see
>> that the Remote API is indeed switched on.
>>
>> When I do a wget from our Jenkins box against JIRA I get told I'm not
>> authenticated - perfect.
>>
>> When I configure the JIRA plugin within Jenkins using my credentials I
>> hit "Validate" and get told Failed to authenticate.
>>
>> Checked the Jenkins logs and I find a stack trace. An HTTP response has
>> been received - HTML output with markup that I've failed to authenticate.
>> The stack trace itself says it expected a JSON response!
>>
>> I'm sure this must be pretty fundamental. Does it somehow require a more
>> recent version of JIRA or something that I've not spotted?
>>
>> Thanks,
>>
>> James
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/d4e39397-8d99-4065-a686-a1659ebb3992%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMH6%2BawjwbNcbZisv0XYxGHZXq7MKsJP5UVGiT%2B0OfSqN_zuwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Shared libraries and very slow aapt cruncher (android)

[Maciej Gąsiorowski]

I think I found a cause, when I remove ansi color wrapper everything works 
:)

W dniu wtorek, 25 lipca 2017 13:43:26 UTC+2 użytkownik Maciej Gąsiorowski 
napisał:
>
> Hi,
>
> I have problem and I have finished with ideas where is problem.
>
> I have shared libraries which build our android appliaction, everything 
> works. But when project uses kotlin and aapt cruncher, cruncher works very 
> slow. My build's timouts after one hour.
>
> When I use the same project with Scripted Pipeline, Freestyle Job, or 
> disable cruncher everything works ok, but not in shared libraries.
>
> How can I find cause of this problem ?
>
> I tried read logs, debug gradle, etc.
>
> My example library looks like this:
>
> def call(body) {
> // evaluate the body block, and collect configuration into the object
> def config = [:]
> body.resolveStrategy = Closure.DELEGATE_FIRST
> body.delegate = config
> body()
>
> timeout(60) {
> node("${config.nodeLabel}") {
> stage("Static analysis") {
> deleteDir()
> unstash "workspace"
> wrap([$class: "AnsiColorBuildWrapper", "colorMapName": 
> "VGA"]) {
> withEnv(["GRADLE_USER_HOME=${env.WORKSPACE}/.gradle"]) {
> sh "chmod +x gradlew"
> sh "./gradlew --info --full-stacktrace 
> --refresh-dependencies --continue -PversionCode=${env.BUILD_NUMBER} clean 
> ${config.gradleTasks}"
> }
> }
> }
> }
> }
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/86c0da59-5ce6-49a9-9b94-ba7cc0162141%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Stuck declarative script

[David Aldrich]

Hi

I have a declarative script job that appears to have got stuck because it's 
slave rebooted. Now I can't kill it.

When I click the red cross against the job I see:

 "Are you sure you want to abort null".

I accept but nothing happens.

It also survives a Jenkins restart. How can I kill it?

Best regards

David

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/f30e15ef53b94ec19476731675d1879a%40EUX13SRV1.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.