[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title ickersep edited a comment on JENKINS-62164 Re: Error after update to 2.222.3 with pinned plugins I discovered that I have several pinned plugins (all with timestamps from 4-5 years ago). After I removed all the *.pinned files Jenkins starts again. This is strange since [https://wiki.jenkins.io/display/JENKINS/Pinned+Plugins] mentions that the pinned plugins feature was removed in Jenkins 2, so I wouldn't have expected that this suddenly causes problems. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206093.1588685014000.21989.1588686840044%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title ickersep commented on JENKINS-62164 Re: Error after update to 2.222.3 with pinned plugins I discovered that I have several pinned plugins (all with timestamps from 4-5 years ago). After I removed all the *.pinned files Jenkins starts again. This is strange since https://wiki.jenkins.io/display/JENKINS/Pinned+Plugins mentions that the pinned plugins feature was removed in Jenkins 2, so I wouldn't have expected that this suddenly causes problems. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206093.1588685014000.21988.1588686780043%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title ickersep updated an issue Jenkins / JENKINS-62164 Error after update to 2.222.3 with pinned plugins Change By: ickersep Summary: Error after update to 2.222.3 with pinned plugins Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206093.1588685014000.21987.1588686660065%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3
Title: Message Title
ickersep updated an issue
Jenkins / JENKINS-62164
Error after update to 2.222.3
Change By:
ickersep
After upgrading to 2.222.3 (from 2. 2 204 . 04. 2) Jenkins fails to load properly and displays this error:{{java.lang.NoClassDefFoundError: Could not initialize class hudson.model.Hudson$MasterComputer}} \ {{ at jenkins.model.Jenkins.createComputer(Jenkins.java:3106)}} \ {{ at hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:136)}} \ {{ at hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:47)}} \ {{ at hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:210)}} \ {{ at hudson.model.Queue._withLock(Queue.java:1399)}} \ {{ at hudson.model.Queue.withLock(Queue.java:1276)}} \ {{ at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:196)}} \ {{ at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1617)}} \ {{ at jenkins.model.Jenkins.(Jenkins.java:998)}} \ {{ at hudson.model.Hudson.(Hudson.java:85)}} \ {{ at hudson.model.Hudson.(Hudson.java:81)}} \ {{ at hudson.WebAppMain$3.run(WebAppMain.java:233)}}{{Caused: hudson.util.HudsonFailedToLoad}} \ {{ at hudson.WebAppMain$3.run(WebAppMain.java:247)}} {{$ java -version}}{{java version "1.8.0_201"}}{{Java(TM) SE Runtime Environment (build 1.8.0_201-b09)}}{{Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)}}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62164) Error after update to 2.222.3
Title: Message Title
ickersep created an issue
Jenkins / JENKINS-62164
Error after update to 2.222.3
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2020-05-05 13:23
Environment:
Ubuntu 18.04
Priority:
Major
Reporter:
ickersep
After upgrading to 2.222.3 (from 2.2.04.2) Jenkins fails to load properly and displays this error: java.lang.NoClassDefFoundError: Could not initialize class hudson.model.Hudson$MasterComputer {{ at jenkins.model.Jenkins.createComputer(Jenkins.java:3106)}} {{ at hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:136)}} {{ at hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:47)}} {{ at hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:210)}} {{ at hudson.model.Queue._withLock(Queue.java:1399)}} {{ at hudson.model.Queue.withLock(Queue.java:1276)}} {{ at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:196)}} {{ at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1617)}} {{ at jenkins.model.Jenkins.(Jenkins.java:998)}} {{ at hudson.model.Hudson.(Hudson.java:85)}} {{ at hudson.model.Hudson.(Hudson.java:81)}} {{ at hudson.WebAppMain$3.run(WebAppMain.java:233)}} Caused: hudson.util.HudsonFailedToLoad {{ at hudson.WebAppMain$3.run(WebAppMain.java:247)}} $ java -version java version "1.8.0_201" Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
[JIRA] (JENKINS-40191) job created by multibranch pipeline created by job dsl script uses wrong github URL
Title: Message Title
ickersep commented on JENKINS-40191
Re: job created by multibranch pipeline created by job dsl script uses wrong github URL
Found a workaround: Instead of:
github {
repoOwner('ermshiperete')
repository('testproject')
scanCredentialsId('72fb065b-94d8-4642-a81e-4ef784922e88')
excludes('tags/*')
}
use this:
git {
remote('https://github.com/ermshiperete/testproject')
credentialsId('72fb065b-94d8-4642-a81e-4ef784922e88')
excludes('tags/*')
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40191) job created by multibranch pipeline created by job dsl script uses wrong github URL
Title: Message Title
ickersep created an issue
Jenkins / JENKINS-40191
job created by multibranch pipeline created by job dsl script uses wrong github URL
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin, workflow-multibranch-plugin
Created:
2016/Dec/02 3:16 PM
Environment:
Jenkins 2.19.4, workflow-multibranch 2.9.2, job-dsl 1.53
Labels:
pipeline
Priority:
Major
Reporter:
ickersep
I have a multibranch pipeline job created by Job DSL that scans a github project. When it tries to build the branch/job created by the multibranch job it fails trying to clone the sources from github: {{ Branch indexing Connecting to https://api.github.com using ermshiperete/** (GitHub ermshiperete for MultiBranch pipeline) Failed to get git executable Cloning the remote Git repository Cloning repository https://api.github.com/ermshiperete/testproject.git > /usr/bin/git init /var/lib/jenkins/workspace/debug-problem_master-GQUYYD4XVJQFT725TUPAFMPJG2KOOKL3LGLL6UY5O7KBRRBJ4TZQ@script # timeout=10 Fetching upstream changes from https://api.github.com/ermshiperete/testproject.git > /usr/bin/git --version # timeout=10 using GIT_ASKPASS to set credentials GitHub ermshiperete for MultiBranch pipeline > /usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/:refs/remotes/origin/ ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/:refs/remotes/origin/" returned status code 128: stdout: stderr:
[JIRA] (JENKINS-40191) job created by multibranch pipeline created by job dsl script uses wrong github URL
Title: Message Title
ickersep updated an issue
Jenkins / JENKINS-40191
job created by multibranch pipeline created by job dsl script uses wrong github URL
Change By:
ickersep
I have a multibranch pipeline job created by Job DSL that scans a github project.When it tries to build the branch/job created by the multibranch job it fails trying to clone the sources from github with: {noformat}stderr: fatal: unable to access 'https://api.github.com/ermshiperete/testproject.git/': The requested URL returned error: 403{noformat}Things work when I create or modify the multibranch pipeline job through the UI, but that's not an option because I have to define it through a job dsl script.The Job DSL script:{code :groovy }multibranchPipelineJob('debug-problem') {branchSources {github {repoOwner('ermshiperete')repository('testproject')scanCredentialsId('72fb065b-94d8-4642-a81e-4ef784922e88')excludes('tags/*')}orphanedItemStrategy {discardOldItems {numToKeep(10)}}triggers {// run once a day if not otherwise runperiodic(1440)}}}{code}Output of failing job:{noformat}Branch indexingConnecting to https://api.github.com using ermshiperete/** (GitHub ermshiperete for MultiBranch pipeline)Failed to get git executableCloning the remote Git repositoryCloning repository https://api.github.com/ermshiperete/testproject.git> /usr/bin/git init /var/lib/jenkins/workspace/debug-problem_master-GQUYYD4XVJQFT725TUPAFMPJG2KOOKL3LGLL6UY5O7KBRRBJ4TZQ@script # timeout=10Fetching upstream changes from https://api.github.com/ermshiperete/testproject.git> /usr/bin/git --version # timeout=10using GIT_ASKPASS to set credentials GitHub ermshiperete for MultiBranch pipeline> /usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: fatal: unable to access 'https://api.github.com/ermshiperete/testproject.git/': The requested URL returned error: 403at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:512)at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054)at
[JIRA] (JENKINS-40191) job created by multibranch pipeline created by job dsl script uses wrong github URL
Title: Message Title
ickersep updated an issue
Jenkins / JENKINS-40191
job created by multibranch pipeline created by job dsl script uses wrong github URL
Change By:
ickersep
I have a multibranch pipeline job created by Job DSL that scans a github project.When it tries to build the branch/job created by the multibranch job it fails trying to clone the sources from github with: {noformat}stderr: fatal: unable to access 'https://api.github.com/ermshiperete/testproject.git/': The requested URL returned error: 403{noformat}Things work when I create or modify the multibranch pipeline job through the UI, but that's not an option because I have to define it through a job dsl script.The Job DSL script:{code :_javascript_ }multibranchPipelineJob('debug-problem') {branchSources {github {repoOwner('ermshiperete')repository('testproject')scanCredentialsId('72fb065b-94d8-4642-a81e-4ef784922e88')excludes('tags/*')}orphanedItemStrategy {discardOldItems {numToKeep(10)}}triggers {// run once a day if not otherwise runperiodic(1440)}}}{code}Output of failing job:{noformat}Branch indexingConnecting to https://api.github.com using ermshiperete/** (GitHub ermshiperete for MultiBranch pipeline)Failed to get git executableCloning the remote Git repositoryCloning repository https://api.github.com/ermshiperete/testproject.git> /usr/bin/git init /var/lib/jenkins/workspace/debug-problem_master-GQUYYD4XVJQFT725TUPAFMPJG2KOOKL3LGLL6UY5O7KBRRBJ4TZQ@script # timeout=10Fetching upstream changes from https://api.github.com/ermshiperete/testproject.git> /usr/bin/git --version # timeout=10using GIT_ASKPASS to set credentials GitHub ermshiperete for MultiBranch pipeline> /usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: fatal: unable to access 'https://api.github.com/ermshiperete/testproject.git/': The requested URL returned error: 403at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:512)at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054)at
[JIRA] (JENKINS-40191) job created by multibranch pipeline created by job dsl script uses wrong github URL
Title: Message Title
ickersep updated an issue
Jenkins / JENKINS-40191
job created by multibranch pipeline created by job dsl script uses wrong github URL
Change By:
ickersep
I have a multibranch pipeline job created by Job DSL that scans a github project.When it tries to build the branch/job created by the multibranch job it fails trying to clone the sources from github with: {noformat}stderr: fatal: unable to access 'https://api.github.com/ermshiperete/testproject.git/': The requested URL returned error: 403{noformat}Things work when I create or modify the multibranch pipeline job through the UI, but that's not an option because I have to define it through a job dsl script.The Job DSL script:{code: groovy _javascript_ }multibranchPipelineJob('debug-problem') {branchSources {github {repoOwner('ermshiperete')repository('testproject')scanCredentialsId('72fb065b-94d8-4642-a81e-4ef784922e88')excludes('tags/*')}orphanedItemStrategy {discardOldItems {numToKeep(10)}}triggers {// run once a day if not otherwise runperiodic(1440)}}}{code}Output of failing job:{noformat}Branch indexingConnecting to https://api.github.com using ermshiperete/** (GitHub ermshiperete for MultiBranch pipeline)Failed to get git executableCloning the remote Git repositoryCloning repository https://api.github.com/ermshiperete/testproject.git> /usr/bin/git init /var/lib/jenkins/workspace/debug-problem_master-GQUYYD4XVJQFT725TUPAFMPJG2KOOKL3LGLL6UY5O7KBRRBJ4TZQ@script # timeout=10Fetching upstream changes from https://api.github.com/ermshiperete/testproject.git> /usr/bin/git --version # timeout=10using GIT_ASKPASS to set credentials GitHub ermshiperete for MultiBranch pipeline> /usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: fatal: unable to access 'https://api.github.com/ermshiperete/testproject.git/': The requested URL returned error: 403at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:512)at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054)at
[JIRA] (JENKINS-40191) job created by multibranch pipeline created by job dsl script uses wrong github URL
Title: Message Title
ickersep updated an issue
Jenkins / JENKINS-40191
job created by multibranch pipeline created by job dsl script uses wrong github URL
Change By:
ickersep
I have a multibranch pipeline job created by Job DSL that scans a github project.When it tries to build the branch/job created by the multibranch job it fails trying to clone the sources from github with: {noformat}stderr: fatal: unable to access 'https://api.github.com/ermshiperete/testproject.git/': The requested URL returned error: 403{noformat} Things work when I create or modify the multibranch pipeline job through the UI , but that's not an option because I have to define it through a job dsl script .The Job DSL script:{code}multibranchPipelineJob('debug-problem') {branchSources {github {repoOwner('ermshiperete')repository('testproject')scanCredentialsId('72fb065b-94d8-4642-a81e-4ef784922e88')excludes('tags/*')}orphanedItemStrategy {discardOldItems {numToKeep(10)}}triggers {// run once a day if not otherwise runperiodic(1440)}}}{code}Output of failing job:{noformat}Branch indexingConnecting to https://api.github.com using ermshiperete/** (GitHub ermshiperete for MultiBranch pipeline)Failed to get git executableCloning the remote Git repositoryCloning repository https://api.github.com/ermshiperete/testproject.git> /usr/bin/git init /var/lib/jenkins/workspace/debug-problem_master-GQUYYD4XVJQFT725TUPAFMPJG2KOOKL3LGLL6UY5O7KBRRBJ4TZQ@script # timeout=10Fetching upstream changes from https://api.github.com/ermshiperete/testproject.git> /usr/bin/git --version # timeout=10using GIT_ASKPASS to set credentials GitHub ermshiperete for MultiBranch pipeline> /usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: fatal: unable to access 'https://api.github.com/ermshiperete/testproject.git/': The requested URL returned error: 403at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:512)at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054)at
[JIRA] (JENKINS-40191) job created by multibranch pipeline created by job dsl script uses wrong github URL
Title: Message Title
ickersep updated an issue
Jenkins / JENKINS-40191
job created by multibranch pipeline created by job dsl script uses wrong github URL
Change By:
ickersep
I have a multibranch pipeline job created by Job DSL that scans a github project.When it tries to build the branch/job created by the multibranch job it fails trying to clone the sources from github with: {noformat} stderr: fatal: unable to access 'https://api.github.com/ermshiperete/testproject.git/': The requested URL returned error: 403 {noformat} Things work when I create or modify the multibranch pipeline job through the UI.The Job DSL script:{code}multibranchPipelineJob('debug-problem') {branchSources {github {repoOwner('ermshiperete')repository('testproject')scanCredentialsId('72fb065b-94d8-4642-a81e-4ef784922e88')excludes('tags/*')}orphanedItemStrategy {discardOldItems {numToKeep(10)}}triggers {// run once a day if not otherwise runperiodic(1440)}}}{code}Output of failing job: {noformat} Branch indexingConnecting to https://api.github.com using ermshiperete/** (GitHub ermshiperete for MultiBranch pipeline)Failed to get git executableCloning the remote Git repositoryCloning repository https://api.github.com/ermshiperete/testproject.git> /usr/bin/git init /var/lib/jenkins/workspace/debug-problem_master-GQUYYD4XVJQFT725TUPAFMPJG2KOOKL3LGLL6UY5O7KBRRBJ4TZQ@script # timeout=10Fetching upstream changes from https://api.github.com/ermshiperete/testproject.git> /usr/bin/git --version # timeout=10using GIT_ASKPASS to set credentials GitHub ermshiperete for MultiBranch pipeline> /usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: fatal: unable to access 'https://api.github.com/ermshiperete/testproject.git/': The requested URL returned error: 403at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315)at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:512)at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054)at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094)at
[JIRA] (JENKINS-40191) job created by multibranch pipeline created by job dsl script uses wrong github URL
Title: Message Title
ickersep updated an issue
Jenkins / JENKINS-40191
job created by multibranch pipeline created by job dsl script uses wrong github URL
Change By:
ickersep
I have a multibranch pipeline job created by Job DSL that scans a github project.When it tries to build the branch/job created by the multibranch job it fails trying to clone the sources from github with :stderr: fatal: unable to access 'https://api.github.com/ermshiperete/testproject.git/': The requested URL returned error: 403 Things work when I create or modify the multibranch pipeline job through the UI.The Job DSL script: { code}multibranchPipelineJob('debug-problem') { branchSources {github {repoOwner('ermshiperete')repository('testproject')scanCredentialsId('72fb065b-94d8-4642-a81e-4ef784922e88')excludes('tags/*')}orphanedItemStrategy {discardOldItems {numToKeep(10)}}triggers {// run once a day if not otherwise runperiodic(1440)}}}{code}Output of failing job: Branch indexingConnecting to https://api.github.com using ermshiperete/** (GitHub ermshiperete for MultiBranch pipeline)Failed to get git executableCloning the remote Git repositoryCloning repository https://api.github.com/ermshiperete/testproject.git > /usr/bin/git init /var/lib/jenkins/workspace/debug-problem_master-GQUYYD4XVJQFT725TUPAFMPJG2KOOKL3LGLL6UY5O7KBRRBJ4TZQ@script # timeout=10Fetching upstream changes from https://api.github.com/ermshiperete/testproject.git > /usr/bin/git --version # timeout=10using GIT_ASKPASS to set credentials GitHub ermshiperete for MultiBranch pipeline > /usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: fatal: unable to access 'https://api.github.com/ermshiperete/testproject.git/': The requested URL returned error: 403 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:512) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108) at
[JIRA] (JENKINS-40191) job created by multibranch pipeline created by job dsl script uses wrong github URL
Title: Message Title
ickersep updated an issue
Jenkins / JENKINS-40191
job created by multibranch pipeline created by job dsl script uses wrong github URL
Change By:
ickersep
I have a multibranch pipeline job created by Job DSL that scans a github project.When it tries to build the branch/job created by the multibranch job it fails trying to clone the sources from github: {{Branch indexingConnecting to https://api.github.com using ermshiperete/** (GitHub ermshiperete for MultiBranch pipeline)Failed to get git executableCloning the remote Git repositoryCloning repository https://api.github.com/ermshiperete/testproject.git > /usr/bin/git init /var/lib/jenkins/workspace/debug-problem_master-GQUYYD4XVJQFT725TUPAFMPJG2KOOKL3LGLL6UY5O7KBRRBJ4TZQ@script # timeout=10Fetching upstream changes from https://api.github.com/ermshiperete/testproject.git > /usr/bin/git --version # timeout=10using GIT_ASKPASS to set credentials GitHub ermshiperete for MultiBranch pipeline > /usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "/usr/bin/git fetch --tags --progress https://api.github.com/ermshiperete/testproject.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: fatal: unable to access 'https://api.github.com/ermshiperete/testproject.git/': The requested URL returned error: 403 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1745) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1489) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:512) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1054) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1094) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:85) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:215) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)GitHub has been notified of this commit’s build resultERROR: nullFinished: FAILURE }}Things work when I create or modify the multibranch pipeline job through the UI.The Job DSL script is:{{ multibranchPipelineJob('debug-problem') { branchSources { github { repoOwner('ermshiperete') repository('testproject') scanCredentialsId('72fb065b-94d8-4642-a81e-4ef784922e88') excludes('tags/*') } orphanedItemStrategy { discardOldItems {numToKeep(10) } } triggers { // run once a day if not otherwise run periodic(1440) }
[JIRA] [ghprb-plugin] (JENKINS-35170) GHPRB latest version incorrectly identifying the base branch for merge
Title: Message Title ickersep commented on JENKINS-35170 Re: GHPRB latest version incorrectly identifying the base branch for merge For me this happens when I define a parameter with the same name as one defined by ghprb-plugin. Things start to work again when I remove the parameter. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger-plugin] (JENKINS-35379) gerrit-trigger no longer triggers build
Title: Message Title ickersep created an issue Jenkins / JENKINS-35379 gerrit-trigger no longer triggers build Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2016/Jun/06 3:26 PM Environment: Jenkins 1.651.2, Gerrit 2.12.2, gerrit-trigger 2.21.0 (without REST API enabled) Priority: Major Reporter: ickersep After updating gerrit-trigger from 2.20.0 to 2.21.0 jobs no longer get triggered when a change gets pushed to Gerrit. Manually trying to trigger a Gerrit event manually doesn't work either. Sometimes it reports that a job was triggered (but that job never appears in the build queue), sometimes it claims that no job was triggered. First I thought it might be caused by our Gerrit version, so I upgraded that from 2.10.5 to 2.12.2, but that didn't help. It worked nicely before the upgrade of gerrit-trigger, and started to work again after I downgraded to 2.20.0.
[JIRA] [core] (JENKINS-33478) Cleaning or deleting workspace fails with non-ASCII filename
Title: Message Title ickersep commented on JENKINS-33478 Re: Cleaning or deleting workspace fails with non-ASCII filename No, I previously overlooked the suggested workaround of JENKINS-12610. So I tried right now and added -Dfile.encoding=UTF-8 to JAVA_ARGS in /etc/default/jenkins, restarted Jenkins and added -Dfile.encoding=UTF-8 to the JVM options in the slave configuration and relaunched the slave. These settings don't make a difference though. It still can't delete the files. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33478) Cleaning or deleting workspace fails with non-ASCII filename
Title: Message Title ickersep updated an issue Jenkins / JENKINS-33478 Cleaning or deleting workspace fails with non-ASCII filename Change By: ickersep Labels: ascii unicode Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33478) Cleaning or deleting workspace fails with non-ASCII filename
Title: Message Title ickersep updated an issue Jenkins / JENKINS-33478 Cleaning or deleting workspace fails with non-ASCII filename Change By: ickersep I have a project in git that contains a file with unicode, non-ASCII characters. The build fails with:ERROR: Failed to clean the workspacejava.io.IOException: java.lang.reflect.InvocationTargetException at hudson.Util.isSymlinkJava7(Util.java:377) at hudson.Util.isSymlink(Util.java:342) at hudson.Util.deleteRecursive(Util.java:308) at hudson.Util.deleteContentsRecursive(Util.java:220) at hudson.Util.deleteRecursive(Util.java:309) at hudson.Util.deleteContentsRecursive(Util.java:220) at hudson.Util.deleteRecursive(Util.java:309) at hudson.Util.deleteContentsRecursive(Util.java:220) at hudson.Util.deleteRecursive(Util.java:309) at hudson.Util.deleteContentsRecursive(Util.java:220) at hudson.Util.deleteRecursive(Util.java:309) at hudson.Util.deleteContentsRecursive(Util.java:220) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:454) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.Util.isSymlinkJava7(Util.java:372) ... 22 moreCaused by: java.nio.file.InvalidPathException: Malformed input or input contains unmappable chacraters: /home/jenkins/workspace/GitHub-LfMerge-Linux-any-master-debug/data/TestLangProj/LinkedFiles/AudioVisual/635460455469905390u ??i??w.wav at sun.nio.fs.UnixPath.encode(UnixPath.java:147) at sun.nio.fs.UnixPath.(UnixPath.java:71) at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:281) at java.io.File.toPath(File.java:2193) ... 26 moreERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Failed to delete workspace at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:457) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at
[JIRA] [core] (JENKINS-33478) Cleaning or deleting workspace fails with non-ASCII filename
Title: Message Title ickersep updated an issue Jenkins / JENKINS-33478 Cleaning or deleting workspace fails with non-ASCII filename Change By: ickersep I have a project in git that contains a file with unicode, non-ASCII characters. The build fails with:ERROR: Failed to clean the workspacejava.io.IOException: java.lang.reflect.InvocationTargetException at hudson.Util.isSymlinkJava7(Util.java:377) at hudson.Util.isSymlink(Util.java:342) at hudson.Util.deleteRecursive(Util.java:308) at hudson.Util.deleteContentsRecursive(Util.java:220) at hudson.Util.deleteRecursive(Util.java:309) at hudson.Util.deleteContentsRecursive(Util.java:220) at hudson.Util.deleteRecursive(Util.java:309) at hudson.Util.deleteContentsRecursive(Util.java:220) at hudson.Util.deleteRecursive(Util.java:309) at hudson.Util.deleteContentsRecursive(Util.java:220) at hudson.Util.deleteRecursive(Util.java:309) at hudson.Util.deleteContentsRecursive(Util.java:220) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:454) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.Util.isSymlinkJava7(Util.java:372) ... 22 moreCaused by: java.nio.file.InvalidPathException: Malformed input or input contains unmappable chacraters: /home/jenkins/workspace/GitHub-LfMerge-Linux-any-master-debug/data/TestLangProj/LinkedFiles/AudioVisual/635460455469905390u ??i??w.wav at sun.nio.fs.UnixPath.encode(UnixPath.java:147) at sun.nio.fs.UnixPath.(UnixPath.java:71) at sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:281) at java.io.File.toPath(File.java:2193) ... 26 moreERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Failed to delete workspace at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:457) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at
[JIRA] [core] (JENKINS-33478) Cleaning workspace fails with non-ASCII filename
Title: Message Title ickersep updated an issue Jenkins / JENKINS-33478 Cleaning workspace fails with non-ASCII filename Change By: ickersep Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33478) Cleaning or deleting workspace fails with non-ASCII filename
Title: Message Title ickersep updated an issue Jenkins / JENKINS-33478 Cleaning or deleting workspace fails with non-ASCII filename Change By: ickersep Summary: Cleaning or deleting workspace fails with non-ASCII filename Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-33478) Cleaning workspace fails with non-ASCII filename
Title: Message Title ickersep created an issue Jenkins / JENKINS-33478 Cleaning workspace fails with non-ASCII filename Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 11/Mar/16 12:19 PM Priority: Blocker Reporter: ickersep I have a project in git that contains a file with unicode, non-ASCII characters. The build fails with: ERROR: Failed to clean the workspace java.io.IOException: java.lang.reflect.InvocationTargetException at hudson.Util.isSymlinkJava7(Util.java:377) at hudson.Util.isSymlink(Util.java:342) at hudson.Util.deleteRecursive(Util.java:308) at hudson.Util.deleteContentsRecursive(Util.java:220) at hudson.Util.deleteRecursive(Util.java:309) at hudson.Util.deleteContentsRecursive(Util.java:220) at hudson.Util.deleteRecursive(Util.java:309) at hudson.Util.deleteContentsRecursive(Util.java:220) at hudson.Util.deleteRecursive(Util.java:309) at hudson.Util.deleteContentsRecursive(Util.java:220) at hudson.Util.deleteRecursive(Util.java:309) at hudson.Util.deleteContentsRecursive(Util.java:220) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:454) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145) at hudson.remoting.UserRequest.perform(UserRequest.java:120) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at
[JIRA] [nodejs-plugin] (JENKINS-27944) Auto-installer list not populating on Ubuntu Server
Title: Message Title ickersep commented on JENKINS-27944 Re: Auto-installer list not populating on Ubuntu Server Any suggestion how the 'Update now' could be triggered programmatically, e.g. from a groovy script? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs-plugin] (JENKINS-31485) NodeJS Invalid Tool ID
Title: Message Title ickersep commented on JENKINS-31485 Re: NodeJS Invalid Tool ID ...and here... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-plugin] (JENKINS-23301) Support unix protocol for connection
Title: Message Title ickersep commented on JENKINS-23301 Re: Support unix protocol for connection I can confirm that it works in the current version. Excellent! However, the help text still says that only http is supported. Would be great if that could be updated and unix:///var/run/docker.sock added as additional example, e.g.: The URL to use to access your Docker server API (e.g: http://172.16.42.43:4243 or unix:///var/run/docker.sock) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27462) Adjust syntax of subviews of nestedView
ickersep
created JENKINS-27462
Adjust syntax of subviews of nestedView
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
17/Mar/15 2:55 PM
Description:
A recent change modified the way views get defined. The subviews of nestedView should be created in the same way.
Currently we have to write:
nestedView('project-a') {
views {
view('pipeline', type: BuildPipelineView) {
selectedJob('project-a-compile')
}
}
}
It would be nicer if it would be:
nestedView('project-a') {
views {
buildPipelineView('pipeline') {
selectedJob('project-a-compile')
} }
}
}
Project:
Jenkins
Priority:
Major
Reporter:
ickersep
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27462) Adjust syntax of subviews of nestedView
ickersep
updated JENKINS-27462
Adjust syntax of subviews of nestedView
Change By:
ickersep
(17/Mar/15 2:57 PM)
Description:
Arecentchangemodifiedthewayviewsgetdefined.ThesubviewsofnestedViewshouldbecreatedinthesameway.Currentlywehavetowrite:
pre
nestedView(project-a){views{view(pipeline,type:BuildPipelineView){selectedJob(project-a-compile)}}}
/pre
Itwouldbenicerifitwouldbe:
pre
nestedView(project-a){views{buildPipelineView(pipeline){selectedJob(project-a-compile)}}}
/pre
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27462) Adjust syntax of subviews of nestedView
ickersep
updated JENKINS-27462
Adjust syntax of subviews of nestedView
Change By:
ickersep
(17/Mar/15 2:56 PM)
Description:
Arecentchangemodifiedthewayviewsgetdefined.ThesubviewsofnestedViewshouldbecreatedinthesameway.Currentlywehavetowrite:
pre
nestedView(project-a){views{view(pipeline,type:BuildPipelineView){selectedJob(project-a-compile)}}}
/pre
Itwouldbenicerifitwouldbe:
pre
nestedView(project-a){views{buildPipelineView(pipeline){selectedJob(project-a-compile)}}}
/pre
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-18464) Build Pipeline and Join plugin do not play nicely together
ickersep commented on JENKINS-18464 Build Pipeline and Join plugin do not play nicely together https://code.google.com/p/build-pipeline-plugin/issues/detail?id=21 describes the same problem. Comment #19 (https://code.google.com/p/build-pipeline-plugin/issues/detail?id=21#c19) has a fix (https://code.google.com/r/jessica-join-support-build-pipeline-plugin/source/detail?r=b15a06a07a24adfc35638c7dd4a93dbd16f52bf6), but it looks it never got integrated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-26424) Abort build option isn't supported for build timeout plugin
ickersep created JENKINS-26424 Abort build option isnt supported for build timeout plugin Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 14/Jan/15 11:27 AM Description: Currently it's not possible to directly specify the AbortBuild option for the build timeout plugin, only FailBuild is possible. Project: Jenkins Priority: Major Reporter: ickersep This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-26423) Support Categorized Job View plugin
ickersep created JENKINS-26423 Support Categorized Job View plugin Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 14/Jan/15 11:23 AM Description: It would be nice if the categorized job view would be supported Project: Jenkins Priority: Major Reporter: ickersep This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release] (JENKINS-13728) Have Role Stragegy support the Release plugin
ickersep updated JENKINS-13728 Have Role Stragegy support the Release plugin Change By: ickersep (25/Sep/14 4:52 PM) Component/s: role-strategy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method #39;next#39; in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=email-body
table id=email-wrap align=center border=0 cellpadding=0
cellspacing=0 style=background-color:#f0f0f0;color:#00;width:100%;
tr valign=top
td id=email-page style=padding:16px !important;
table align=center border=0 cellpadding=0 cellspacing=0
style=background-color:#ff;border:1px solid
#bb;color:#00;width:100%;
tr valign=top
td bgcolor=#33
style=background-color:#33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;img
src=https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png;
alt= style=vertical-align:top; //td
/trtr valign=top
td id=email-banner style=padding:32px 32px 0 32px;
table align=left border=0 cellpadding=0 cellspacing=0
width=100% style=width:100%;
tr valign=top
td
style=color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;
img id=email-avatar
src=https://issues.jenkins-ci.org/secure/useravatar?avatarId=10292; alt=
height=48 width=48 border=0 align=left style=padding:0;margin: 0 16px
16px 0; /
div id=email-action style=padding: 0 0 8px
0;font-size:12px;line-height:18px;
a class=user-hover rel=ickersep
id=email_ickersep
href=https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=ickersep;
style=color:#355564;ickersep/a
commented on img src=https://issues.jenkins-ci.org/images/icons/bug.gif;
height=16 width=16 border=0 align=absmiddle alt=Bug a
style='color:#355564;text-decoration:none;'
href='https://issues.jenkins-ci.org/browse/JENKINS-5323'JENKINS-5323/a
/div
[JIRA] [core] (JENKINS-5323) within 1 executor: job started while post-actions of previous job still running
ickersep updated JENKINS-5323 within 1 executor: job started while post-actions of previous job still running Change By: ickersep (17/May/13 9:28 PM) Environment: Win200364-bit,with64-bitJVM,Hudson1.338 Win764-bit,Jenkins1.514,Executeconcurrentbuildsenabled Priority: Major Critical Description: Oneexecutorononemachine:FinishesjobA,startsthepost-build-actionsofjobAandwhiletheyarestillrunningstartsjobB.WehaveoneHudsonmasterandseveralHudsonclients.Theyallonlyhave1executorpermachinesoononemachineofficiallyonlyonejobrunsatatime.ExampleofthetimingoftwosubsequentjobswithallHudsonnodesofflineexceptone(andrememberweonlyhave1executorpermachine!):0:59am:puttingtwojobsintothequeue:Job1andJob21:00am:Job1starts...2:00am:Job1finishedexecutingallbuildsteps2:00am:Job1postbuildactionsstart...2:01am:Job2starts...2:03am:Job1postbuildactionsfinishedAsyoucanseefrom2:01amtill2:03amJob2andthepost-build-actionsofJob1arerunninginparallelonthesameexecutor!ThatstheproblemIamtalkingabout.Wehavethefollowingpost-buildactionsenabled:*Archivetheartifacts*PublishJUnittestresultreport(Thisistheonewhichtriedtoaccessfileswhichwerenolongertherethen.)*E-mailNotificationAsfarasIunderstandlocks+latcheswontdowhatwewanttohappenbecausewewanttohaveJob1andJob2runinparallelindifferentexecutors/machinesiftherearemoreexecutors/machinesonline.Thefirstthingajobdoesistodeletealltheworkspacesonthatmachineexcepthisownone.Wedothatbecausetheclientsdisksaretoosmalltoholdalljobsworkspaces.(Eachjobsworkspaceisabout10GBandwehaveabout100jobs,butthediskoftheHudsonmachineisjust100GB.)Butthisdeletionisactuallyjustwhatmadeusrealizeabouttheparallelism.ThebugIwanttoreportisthatJob1-post-build-actionsruninparallelwithJob2onthesamemachinewithjustoneexecutor.youmightwanttoseethediscussionontheuserslistregardingtheissue:http:// jenkins.361315. n4.nabble.com/Post-actions-still-run-while-next-job-already-started-td1013097.html Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-5323) within 1 executor: job started while post-actions of previous job still running
ickersep edited a comment on JENKINS-5323 within 1 executor: job started while post-actions of previous job still running We experience the same problem, also on Windows, but with multiple executors. This is really annoying because regularly builds fail because of this bug. We have "Execute concurrent builds if necessary" enabled for the job in question. We use git with the "clean workspace" option enabled which deletes the files the previous build still requires in it's post-actions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-5323) within 1 executor: job started while post-actions of previous job still running
ickersep edited a comment on JENKINS-5323 within 1 executor: job started while post-actions of previous job still running We experience the same problem, also on Windows, but with multiple executors. This is really annoying because regularly builds fail because of this bug. We have "Execute concurrent builds if necessary" enabled for the job in question. We use git with the "clean workspace" option enabled which deletes the files the previous build still requires in it's post-actions. The scenario is this: job1-build1 finishes the build steps job1-build1 starts the post-build actions job1-build2 starts and does a "git clean -dxf" deleting all built files from the workspace job1-build1 finishes post-build actions (or rather crashes) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [concurrent-build] (JENKINS-5323) within 1 executor: job started while post-actions of previous job still running
ickersep updated JENKINS-5323 within 1 executor: job started while post-actions of previous job still running Change By: ickersep (17/May/13 9:36 PM) Component/s: concurrent-build This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [concurrent-build] (JENKINS-5323) within 1 executor: job started while post-actions of previous job still running
ickersep edited a comment on JENKINS-5323 within 1 executor: job started while post-actions of previous job still running We experience the same problem, also on Windows. While the original bug report mentioned one executor running multiple jobs, we have multiple executors but only one job. We trigger builds when a change gets uploaded to Gerrit. When enough changes get uploaded at the right time a build will start on an executor that is still running the post-build actions of a previous build. This is really annoying because builds fail regularly because of this bug. We have "Execute concurrent builds if necessary" enabled for the job in question. We use git with the "clean workspace" option enabled which deletes the files the previous build still requires in its post-actions. The scenario is this: job1-build1 finishes the build steps job1-build1 starts the post-build actions job1-build2 starts and does a "git clean -dxf" deleting all built files from the workspace job1-build1 finishes post-build actions (or rather crashes) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17212) Git clean broken on Windows
ickersep commented on JENKINS-17212 Git clean broken on Windows Unfortunately I still get the same failure with the snapshot build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17212) Git clean broken on Windows
ickersep created JENKINS-17212 Git clean broken on Windows Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 14/Mar/13 11:20 AM Description: Since the update of the Git Client plugin to 1.0.4 git clean doesn't work anymore on Windows build agents. It fails with (the file being different between different tries): Cleaning workspace FATAL: Could not delete file C:\JenkinsSlaveHome\slave2\workspace\Somejob\tmp\Store1\trash org.eclipse.jgit.api.errors.JGitInternalException: Could not delete file C:\JenkinsSlaveHome\slave2\workspace\Somejob\tmp\Store1\trash at org.eclipse.jgit.api.CleanCommand.call(CleanCommand.java:137) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.clean(JGitAPIImpl.java:305) at hudson.plugins.git.GitAPI.clean(GitAPI.java:248) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1213) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1196) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: Could not delete file C:\JenkinsSlaveHome\slave2\workspace\Gerrit-FieldWorks-Win-any-develop-debug\tmp\Store1\trash at org.eclipse.jgit.util.FileUtils.delete(FileUtils.java:142) at org.eclipse.jgit.api.CleanCommand.call(CleanCommand.java:132) ... 14 more Environment: Windows Project: Jenkins Priority: Major Reporter: ickersep This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17212) Git clean broken on Windows
ickersep updated JENKINS-17212 Git clean broken on Windows Change By: ickersep (14/Mar/13 11:24 AM) Description: SincetheupdateoftheGitClientpluginto1.0.4gitclean (Cleanaftercheckout) doesntworkanymoreonWindowsbuildagents.Itfailswith(thefilebeingdifferentbetweendifferenttries):CleaningworkspaceFATAL:CouldnotdeletefileC:\JenkinsSlaveHome\slave2\workspace\Somejob\tmp\Store1\trashorg.eclipse.jgit.api.errors.JGitInternalException:CouldnotdeletefileC:\JenkinsSlaveHome\slave2\workspace\Somejob\tmp\Store1\trash atorg.eclipse.jgit.api.CleanCommand.call(CleanCommand.java:137) atorg.jenkinsci.plugins.gitclient.JGitAPIImpl.clean(JGitAPIImpl.java:305) athudson.plugins.git.GitAPI.clean(GitAPI.java:248) athudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1213) athudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1196) athudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) atjava.util.concurrent.FutureTask$Sync.innerRun(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor.runWorker(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) atjava.lang.Thread.run(UnknownSource)Causedby:java.io.IOException:CouldnotdeletefileC:\JenkinsSlaveHome\slave2\workspace\Gerrit-FieldWorks-Win-any-develop-debug\tmp\Store1\trash atorg.eclipse.jgit.util.FileUtils.delete(FileUtils.java:142) atorg.eclipse.jgit.api.CleanCommand.call(CleanCommand.java:132) ...14more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17216) Triggering on files not working
ickersep created JENKINS-17216 Triggering on files not working Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 14/Mar/13 5:00 PM Description: I'd like to trigger a build when any file under Build/Agent/ changes. For that I have the setting for File: Path=Build/Agent/* in the gerrit-plugin section of the job config (in addition to the project and several branches). In the git section I have Included Regions: Build/Agent/*. I would expect that it triggers a build only when a file under Build/Agent/ changes. Instead it triggers a build on any change. In case it matters: it's a multi-configuration project. Environment: gerrit-trigger 2.9.0, Gerrit 2.5.2 Project: Jenkins Priority: Major Reporter: ickersep This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15362) Regexp for file in trigger pattern
ickersep resolved JENKINS-15362 as Fixed Regexp for file in trigger pattern This got changed on the wiki page to f~.*\.txt in December. Change By: ickersep (14/Mar/13 5:14 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16993) Publish Build - Discard Old Builds throws exception
ickersep closed JENKINS-16993 as Fixed Publish Build - Discard Old Builds throws exception Thanks for the quick fix! Change By: ickersep (01/Mar/13 7:04 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16993) Publish Build - Discard Old Builds throws exception
ickersep created JENKINS-16993 Publish Build - Discard Old Builds throws exception Issue Type: Bug Assignee: vjuranek Components: build-publisher Created: 28/Feb/13 7:50 AM Description: On saving changes with Publish Build - Discard Old Changes the following exception is thrown: Status Code: 500 Exception: java.lang.NoSuchFieldError: DESCRIPTOR Stacktrace: javax.servlet.ServletException: java.lang.NoSuchFieldError: DESCRIPTOR at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at
[JIRA] (JENKINS-16927) TmpCleaner cleans to much on Windows
ickersep created JENKINS-16927 TmpCleaner cleans to much on Windows Issue Type: Bug Assignee: Unassigned Components: tmpcleaner Created: 22/Feb/13 9:28 AM Description: On a Windows build agent/slave the tmpcleaner plugin seems to delete to much in the user's home directory. I saw it delete files in %USERPROFILE%\AppData and %USERPROFILE%\Documents. This should be limited to the tmp directory (%USERPROFILE%\AppData\Local\Temp, and/or the directory %TMP% or %TEMP% points to). Project: Jenkins Priority: Major Reporter: ickersep This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15569) draft-published trigger doesn't work
ickersep created JENKINS-15569 draft-published trigger doesnt work Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 18/Oct/12 2:27 PM Description: I can't get triggering on draft-published to work. Environment: Gerrit 2.5-rc1 Project: Jenkins Priority: Major Reporter: ickersep This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
