[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title Daniel Jeznach commented on JENKINS-56809 Re: No lastCompletedBuild symlink I need to access files directly on filesystem This is not supported. If somehow works this way for you, fine, but it may not, or may stop working in the future. I'm fully aware, that it's not supported. I saw the missing links issue has been fixed, thank you. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.198459.1553858983000.7591.1569826740189%40Atlassian.JIRA.
[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title
Daniel Jeznach edited a comment on JENKINS-56809
Re: No lastCompletedBuild symlink
Thanks for explaining. Still, I don't see new solution handles lastCompletedBuild.Copy Artifact does not satisfy me, because I need to access files directly on filesystem, before jenkins handles it (I use reverse proxy to intercept /artifact/ url.For my test job, I found there is permalinks file created, which can be use as symlinks equivalent, this is great, so I don't need to install plugin, but its contents is:{{lastFailedBuild -1}} {{lastStableBuild 2}} {{lastSuccessfulBuild 2}} {{lastUnstableBuild -1}} {{lastUnsuccessfulBuild -1}}As you can see, no lastCompletedBuild entry, but when I type lastCompletedBuild in build URL (/job/test/lastCompletedBuild/) , it's handled correctly. So it seems inconsistent to me.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.198459.1553858983000.5709.1569482700284%40Atlassian.JIRA.
[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title Daniel Jeznach updated JENKINS-56809 Jenkins / JENKINS-56809 No lastCompletedBuild symlink Change By: Daniel Jeznach Resolution: Won't Fix Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.198459.1553858983000.5710.1569482700356%40Atlassian.JIRA.
[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title
Daniel Jeznach edited a comment on JENKINS-56809
Re: No lastCompletedBuild symlink
Thanks for explaining. Still, I don't see new solution handles lastCompletedBuild.Copy Artifact does not satisfy me, because I need to access files directly on filesystem, before jenkins handles it (I use reverse proxy to intercept /artifact/ url ) .For my test job, I found there is permalinks file created, which can be use as symlinks equivalent, this is great, so I don't need to install plugin, but its contents is:{{lastFailedBuild -1}} {{lastStableBuild 2}} {{lastSuccessfulBuild 2}} {{lastUnstableBuild -1}} {{lastUnsuccessfulBuild -1}}As you can see, no lastCompletedBuild entry, but when I type lastCompletedBuild in build URL (/job/test/lastCompletedBuild/), it's handled correctly. So it seems inconsistent to me.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.198459.1553858983000.5712.1569482700384%40Atlassian.JIRA.
[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title
Daniel Jeznach edited a comment on JENKINS-56809
Re: No lastCompletedBuild symlink
Thanks for explaining. Still, I don't see new solution handles lastCompletedBuild.Copy Artifact does not satisfy me, because I need to access files directly on filesystem, before jenkins handles it (I use reverse proxy to intercept /artifact/ url.For my test job, I found there is permalinks file created, which can be use as symlinks equivalent, this is great, so I don't need to install plugin, but its contents is:{{lastFailedBuild -1}}{{lastStableBuild 2}}{{lastSuccessfulBuild 2}}{{lastUnstableBuild -1}}{{lastUnsuccessfulBuild -1}} As you can see, no lastCompletedBuild entry, but when I type lastCompletedBuild in build URL, it's handled correctly. So it seems inconsistent to me.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.198459.1553858983000.5707.1569482640122%40Atlassian.JIRA.
[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title Daniel Jeznach commented on JENKINS-56809 Re: No lastCompletedBuild symlink Thanks for explaining. Still, I don't see new solution handles lastCompletedBuild. Copy Artifact does not satisfy me, because I need to access files directly on filesystem, before jenkins handles it (I use reverse proxy to intercept /artifact/ url. For my test job, I found there is permalinks file created, which can be use as symlinks equivalent, this is great, so I don't need to install plugin, but its contents is: lastFailedBuild -1 lastStableBuild 2 lastSuccessfulBuild 2 lastUnstableBuild -1 lastUnsuccessfulBuild -1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.198459.1553858983000.5705.1569482580127%40Atlassian.JIRA.
[JIRA] (JENKINS-58290) WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator
Title: Message Title Daniel Jeznach commented on JENKINS-58290 Re: WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator Jesse Glick Yes, pkill was guilty in this case. Thank you for quick and accurate response. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.200355.156202156.6147.1564731960105%40Atlassian.JIRA.
[JIRA] (JENKINS-58290) WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator
Title: Message Title
Daniel Jeznach edited a comment on JENKINS-58290
Re: WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator
Hello, fix for this issue causes one of our pipelines to stuck. Passing {noformat}-Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true{noformat} parameter reverts to old behavior, so I blame running sh build step in subshell as a cause of this.Pipeline code is:{code:java}pipeline {agent { label "xx" + (env.JOB_NAME.find(/-(u14|u16|u18|w7|w10)(?=-)/) ?:'') }options {timeout(time: 60, unit: 'MINUTES')}environment {TMP = "${env.WORKSPACE}/tmp"PROJECT_NAME = "${env.JOB_NAME}".find(/^[^-]+/)PROJECT_BRANCH = "${env.JOB_NAME}".find(/(?<=^[^-]+-)[^-]+/)PROJECT_RELEASE = "${env.PROJECT_BRANCH}".replace('MAIN', 'rc')P4_BRANCH = "REL/${env.PROJECT_BRANCH}".replace('REL/MAIN', 'MAIN')}parameters {string(name: 'change', defaultValue: '', description: 'Changelist to build.', trim: true)string(name: 'status', defaultValue: '', description: 'Changelist status (shelved/submitted).', trim: true)string(name: 'review', defaultValue: '', description: 'Helix Swarm review number.', trim: true)string(name: 'pass', defaultValue: '', description: 'Success callback URL.', trim: true)string(name: 'fail', defaultValue: '', description: 'Failure callback URL.', trim: true)}triggers {pollSCM('@midnight')}stages {stage('sync') {steps {p4sync(credential: 'x',format: '.-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}_ws',populate: forceClean(),source: depotSource("//path/${env.P4_BRANCH}/..."))buildName "${env.P4_CHANGELIST} ${params.status?:''} ${params.change?:''}".trim()sh '''sed 's/\\\$Change: [0-9]\\+ \\\$/\$Change: '$P4_CHANGELIST' \$/' -i x/version.py'''script {def dot = env.PROJECT_RELEASE.find(/rc$/) ? '' : '.'env.PACKAGE_NAME = "${env.PROJECT_NAME}-${env.PROJECT_RELEASE}${dot}${env.P4_CHANGELIST}.tar.gz"}echo "PROJECT_NAME = $PROJECT_NAME"echo "PROJECT_BRANCH = $PROJECT_BRANCH"echo "PROJECT_RELEASE = $PROJECT_RELEASE"echo "P4_BRANCH = $P4_BRANCH"echo "PACKAGE_NAME = $PACKAGE_NAME"}}stage('build') {steps { sh '''#!/bin/bash -xe# Clean up possible orphans from other test sessionspkill -P1 -U $(id -u) || truemkdir $TMPvirtualenv venv. venv/bin/activatepython setup.py sdistpip install dist/${PROJECT_NAME}-${PROJECT_RELEASE}*.tar.gzxx master --print-requirements | xargs pip installpip install -r tests/test_requirements.txt'''}}stage('test') { steps { sh '''. venv/bin/activatepytest -n 4 \ --timeout=300 \ --junit-xml ${WORKSPACE}/testresults.xml \ --verbose \ --cov=${PROJECT_NAME} \ --cov-branch \ --cov-report xml:${WORKSPACE}/coverage.xml \
[JIRA] (JENKINS-58290) WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-58290
WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator
Change By:
Daniel Jeznach
Comment:
Hello, fix for this issue causes one of our pipelines to stuck. Passing {noformat}-Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true{noformat} parameter reverts to old behavior, so I blame running sh build step in subshell as a cause of this.Pipeline code is:{code:java}pipeline {agent { label "xx" + (env.JOB_NAME.find(/-(u14|u16|u18|w7|w10)(?=-)/) ?:'') }options {timeout(time: 60, unit: 'MINUTES')}environment {TMP = "${env.WORKSPACE}/tmp"PROJECT_NAME = "${env.JOB_NAME}".find(/^[^-]+/)PROJECT_BRANCH = "${env.JOB_NAME}".find(/(?<=^[^-]+-)[^-]+/)PROJECT_RELEASE = "${env.PROJECT_BRANCH}".replace('MAIN', 'rc')P4_BRANCH = "REL/${env.PROJECT_BRANCH}".replace('REL/MAIN', 'MAIN')}parameters {string(name: 'change', defaultValue: '', description: 'Changelist to build.', trim: true)string(name: 'status', defaultValue: '', description: 'Changelist status (shelved/submitted).', trim: true)string(name: 'review', defaultValue: '', description: 'Helix Swarm review number.', trim: true)string(name: 'pass', defaultValue: '', description: 'Success callback URL.', trim: true)string(name: 'fail', defaultValue: '', description: 'Failure callback URL.', trim: true)}triggers {pollSCM('@midnight')}stages {stage('sync') {steps {p4sync(credential: 'x',format: '.-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}_ws',populate: forceClean(),source: depotSource("//path/${env.P4_BRANCH}/..."))buildName "${env.P4_CHANGELIST} ${params.status?:''} ${params.change?:''}".trim()sh '''sed 's/\\\$Change: [0-9]\\+ \\\$/\$Change: '$P4_CHANGELIST' \$/' -i x/version.py'''script {def dot = env.PROJECT_RELEASE.find(/rc$/) ? '' : '.'env.PACKAGE_NAME = "${env.PROJECT_NAME}-${env.PROJECT_RELEASE}${dot}${env.P4_CHANGELIST}.tar.gz"}echo "PROJECT_NAME = $PROJECT_NAME"echo "PROJECT_BRANCH = $PROJECT_BRANCH"echo "PROJECT_RELEASE = $PROJECT_RELEASE"echo "P4_BRANCH = $P4_BRANCH"echo "PACKAGE_NAME = $PACKAGE_NAME"}}stage('build') {steps { sh '''#!/bin/bash -xe# Clean up possible orphans from other test sessionspkill -P1 -U $(id -u) || truemkdir $TMPvirtualenv venv. venv/bin/activatepython setup.py sdistpip install dist/${PROJECT_NAME}-${PROJECT_RELEASE}*.tar.gzimgee master --print-requirements | xargs pip installpip install -r tests/test_requirements.txt'''
[JIRA] (JENKINS-58290) WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator
Title: Message Title
Daniel Jeznach commented on JENKINS-58290
Re: WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator
Hello, fix for this issue causes one of our pipelines to stuck. Passing
-Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true
parameter reverts to old behavior, so I blame running sh build step in subshell as a cause of this. Pipeline code is:
pipeline {
agent { label "xx" + (env.JOB_NAME.find(/-(u14|u16|u18|w7|w10)(?=-)/) ?:'') }
options {
timeout(time: 60, unit: 'MINUTES')
}
environment {
TMP = "${env.WORKSPACE}/tmp"
PROJECT_NAME = "${env.JOB_NAME}".find(/^[^-]+/)
PROJECT_BRANCH = "${env.JOB_NAME}".find(/(?<=^[^-]+-)[^-]+/)
PROJECT_RELEASE = "${env.PROJECT_BRANCH}".replace('MAIN', 'rc')
P4_BRANCH = "REL/${env.PROJECT_BRANCH}".replace('REL/MAIN', 'MAIN')
}
parameters {
string(name: 'change', defaultValue: '', description: 'Changelist to build.', trim: true)
string(name: 'status', defaultValue: '', description: 'Changelist status (shelved/submitted).', trim: true)
string(name: 'review', defaultValue: '', description: 'Helix Swarm review number.', trim: true)
string(name: 'pass', defaultValue: '', description: 'Success callback URL.', trim: true)
string(name: 'fail', defaultValue: '', description: 'Failure callback URL.', trim: true)
}
triggers {
pollSCM('@midnight')
}
stages {
stage('sync') {
steps {
p4sync(
credential: 'x',
format: '.-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}_ws',
populate: forceClean(),
source: depotSource("//path/${env.P4_BRANCH}/...")
)
buildName "${env.P4_CHANGELIST} ${params.status?:''} ${params.change?:''}".trim()
sh '''sed 's/\\\$Change: [0-9]\\+ \\\$/\$Change: '$P4_CHANGELIST' \$/' -i x/version.py'''
script {
def dot = env.PROJECT_RELEASE.find(/rc$/) ? '' : '.'
env.PACKAGE_NAME = "${env.PROJECT_NAME}-${env.PROJECT_RELEASE}${dot}${env.P4_CHANGELIST}.tar.gz"
}
echo "PROJECT_NAME = $PROJECT_NAME"
echo "PROJECT_BRANCH = $PROJECT_BRANCH"
echo "PROJECT_RELEASE = $PROJECT_RELEASE"
echo "P4_BRANCH = $P4_BRANCH"
echo "PACKAGE_NAME = $PACKAGE_NAME"
}
}
stage('build') {
steps {
sh '''
#!/bin/bash -xe
# Clean up possible orphans from other test sessions
pkill -P1 -U $(id -u) || true
mkdir $TMP
virtualenv venv
. venv/bin/activate
python setup.py sdist
pip install dist/${PROJECT_NAME}-${PROJECT_RELEASE}*.tar.gz
xx master --print-requirements | xargs pip install
[JIRA] (JENKINS-58290) WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator
Title: Message Title
Daniel Jeznach commented on JENKINS-58290
Re: WebSocket / OkHttp thread leak from BourneShellScript + ContainerExecDecorator
Hello, fix for this issue causes one of our pipelines to stuck. Passing
-Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true
parameter reverts to old behavior, so I blame running sh build step in subshell as a cause of this. Pipeline code is:
pipeline {
agent { label "xx" + (env.JOB_NAME.find(/-(u14|u16|u18|w7|w10)(?=-)/) ?:'') }
options {
timeout(time: 60, unit: 'MINUTES')
}
environment {
TMP = "${env.WORKSPACE}/tmp"
PROJECT_NAME = "${env.JOB_NAME}".find(/^[^-]+/)
PROJECT_BRANCH = "${env.JOB_NAME}".find(/(?<=^[^-]+-)[^-]+/)
PROJECT_RELEASE = "${env.PROJECT_BRANCH}".replace('MAIN', 'rc')
P4_BRANCH = "REL/${env.PROJECT_BRANCH}".replace('REL/MAIN', 'MAIN')
}
parameters {
string(name: 'change', defaultValue: '', description: 'Changelist to build.', trim: true)
string(name: 'status', defaultValue: '', description: 'Changelist status (shelved/submitted).', trim: true)
string(name: 'review', defaultValue: '', description: 'Helix Swarm review number.', trim: true)
string(name: 'pass', defaultValue: '', description: 'Success callback URL.', trim: true)
string(name: 'fail', defaultValue: '', description: 'Failure callback URL.', trim: true)
}
triggers {
pollSCM('@midnight')
}
stages {
stage('sync') {
steps {
p4sync(
credential: 'x',
format: '.-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}_ws',
populate: forceClean(),
source: depotSource("//path/${env.P4_BRANCH}/...")
)
buildName "${env.P4_CHANGELIST} ${params.status?:''} ${params.change?:''}".trim()
sh '''sed 's/\\\$Change: [0-9]\\+ \\\$/\$Change: '$P4_CHANGELIST' \$/' -i x/version.py'''
script {
def dot = env.PROJECT_RELEASE.find(/rc$/) ? '' : '.'
env.PACKAGE_NAME = "${env.PROJECT_NAME}-${env.PROJECT_RELEASE}${dot}${env.P4_CHANGELIST}.tar.gz"
}
echo "PROJECT_NAME = $PROJECT_NAME"
echo "PROJECT_BRANCH = $PROJECT_BRANCH"
echo "PROJECT_RELEASE = $PROJECT_RELEASE"
echo "P4_BRANCH = $P4_BRANCH"
echo "PACKAGE_NAME = $PACKAGE_NAME"
}
}
stage('build') {
steps {
sh '''
#!/bin/bash -xe
# Clean up possible orphans from other test sessions
pkill -P1 -U $(id -u) || true
mkdir $TMP
virtualenv venv
. venv/bin/activate
python setup.py sdist
pip install dist/${PROJECT_NAME}-${PROJECT_RELEASE}*.tar.gz
imgee master --print-requirements | xargs pip install
[JIRA] (JENKINS-50792) Overall Admin access is required to create/copy a job, which wasn't required earlier
Title: Message Title Daniel Jeznach commented on JENKINS-50792 Re: Overall Admin access is required to create/copy a job, which wasn't required earlier The same here: Jenkins 2.164.2, ownership plugin v0.12.1 Stack traceAlso: hudson.security.AccessDeniedException2: pvrqa.jenkins is missing the Overall/Administer permissionat hudson.security.ACL.checkPermission(ACL.java:73)at hudson.security.AccessControlled.checkPermission(AccessControlled.java:47)at com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.throwIfMissingPermission(OwnershipDescription.java:424)java.io.InvalidObjectException: Cannot modify permissions of Jenkins of type class hudson.model.Hudson: pvrqa.jenkins is missing the Overall/Administer permissionat com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.throwIfMissingPermission(OwnershipDescription.java:434)at com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.checkUnsecuredConfiguration(OwnershipDescription.java:419)at com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve(OwnershipDescription.java:382)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:498)at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(SerializationMethodInvoker.java:66)Caused: com.thoughtworks.xstream.converters.reflection.ObjectAccessException: Could not call com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve() : Cannot modify permissions of Jenkins of type class hudson.model.Hudson: pvrqa.jenkins is missing the Overall/Administer permissionat com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(SerializationMethodInvoker.java:72)at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:271)at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72)Caused: com.thoughtworks.xstream.converters.ConversionException: Could not call com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve() : Cannot modify permissions of Jenkins of type class hudson.model.Hudson: pvrqa.jenkins is missing the Overall/Administer permission : Could not call com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve() : Cannot modify permissions of Jenkins of type class hudson.model.Hudson: pvrqa.jenkins is missing the Overall/Administer permission Debugging information message : Could not call com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve() : Cannot modify permissions of Jenkins of type class hudson.model.Hudson: pvrqa.jenkins is missing the Overall/Administer permissioncause-exception : com.thoughtworks.xstream.converters.reflection.ObjectAccessExceptioncause-message : Could not call com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve() : Cannot modify permissions of Jenkins of type class hudson.model.Hudson: pvrqa.jenkins is missing the Overall/Administer permissionclass : com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescriptionrequired-type : com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescriptionconverter-type :
[JIRA] (JENKINS-50792) Overall Admin access is required to create/copy a job, which wasn't required earlier
Title: Message Title
Daniel Jeznach edited a comment on JENKINS-50792
Re: Overall Admin access is required to create/copy a job, which wasn't required earlier
The same here: Jenkins 2.164.2, ownership plugin v0.12.1 { code:java noformat }Stack traceAlso traceAlso : hudson.security.AccessDeniedException2: pvrqa.jenkins is missing the Overall/Administer permission at hudson.security.ACL.checkPermission(ACL.java:73) at hudson.security.AccessControlled.checkPermission(AccessControlled.java:47) at com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.throwIfMissingPermission(OwnershipDescription.java:424) java.io.InvalidObjectException: Cannot modify permissions of Jenkins of type class hudson.model.Hudson: pvrqa.jenkins is missing the Overall/Administer permission at com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.throwIfMissingPermission(OwnershipDescription.java:434) at com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.checkUnsecuredConfiguration(OwnershipDescription.java:419) at com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve(OwnershipDescription.java:382) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(SerializationMethodInvoker.java:66) Caused: com.thoughtworks.xstream.converters.reflection.ObjectAccessException: Could not call com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve() : Cannot modify permissions of Jenkins of type class hudson.model.Hudson: pvrqa.jenkins is missing the Overall/Administer permission at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callReadResolve(SerializationMethodInvoker.java:72) at hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:271) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) Caused: com.thoughtworks.xstream.converters.ConversionException: Could not call com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve() : Cannot modify permissions of Jenkins of type class hudson.model.Hudson: pvrqa.jenkins is missing the Overall/Administer permission : Could not call com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve() : Cannot modify permissions of Jenkins of type class hudson.model.Hudson: pvrqa.jenkins is missing the Overall/Administer permission Debugging information message : Could not call com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve() : Cannot modify permissions of Jenkins of type class hudson.model.Hudson: pvrqa.jenkins is missing the Overall/Administer permissioncause permissioncause -exception : com.thoughtworks.xstream.converters.reflection. ObjectAccessExceptioncause ObjectAccessExceptioncause -message : Could not call com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve() : Cannot modify permissions of Jenkins of type class hudson.model.Hudson: pvrqa.jenkins is missing the Overall/Administer permissionclass permissionclass : com.synopsys.arc.jenkins.plugins.ownership. OwnershipDescriptionrequired OwnershipDescriptionrequired -type : com.synopsys.arc.jenkins.plugins.ownership. OwnershipDescriptionconverter
[JIRA] (JENKINS-56809) No lastCompletedBuild symlink
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-56809
No lastCompletedBuild symlink
Change By:
Daniel Jeznach
I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url {{ JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext }} But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:{{/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext}}On disk, lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. To sum up: it works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.Is it intentional?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-56809) No lastCompletedBuild symlink
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-56809
No lastCompletedBuild symlink
Change By:
Daniel Jeznach
I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url {{ JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext }} But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:{{/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext}}On disk, lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. To sum up: it works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.Is it intentional?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-56809) No lastCompletedBuild symlink
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-56809
No lastCompletedBuild symlink
Change By:
Daniel Jeznach
I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url {{ JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext }} But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:{{/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext}} but On disk, lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. It To sum up: it works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.Is it intentional?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-56809) No lastCompletedBuild symlink
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-56809
No lastCompletedBuild symlink
Change By:
Daniel Jeznach
I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure.Using jenkins UI I can access artifacts via http url JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.extBut I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path: {{ /mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext }} but lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild.It works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All short url shorthand urls from job page have their respective symlinks created, except lastCompletedBuild.Is it intentional?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-56809) No lastCompletedBuild symlink
Title: Message Title Daniel Jeznach updated an issue Jenkins / JENKINS-56809 No lastCompletedBuild symlink Change By: Daniel Jeznach I maintain few jenkinses, various versions (2.x). Some of jobs on them publish artifacts even when build result is failure.Using jenkins UI I can access artifacts via http url JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.extBut I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path:/mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.extbut lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild.It works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild.All short url from job page have their respective symlinks except lastCompletedBuild.Is it intentional? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56809) No lastCompletedBuild symlink
Title: Message Title Daniel Jeznach updated an issue Jenkins / JENKINS-56809 No lastCompletedBuild symlink Change By: Daniel Jeznach Labels: symlink Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-56809) No lastCompletedBuild symlink
Title: Message Title Daniel Jeznach created an issue Jenkins / JENKINS-56809 No lastCompletedBuild symlink Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-03-29 11:29 Environment: Jenkins 2.46.2 openjdk 1.8.0 ubnutu 16.04 lts Priority: Minor Reporter: Daniel Jeznach I maintain few jenkinses, various versions (2.x). Some of them publish artifacts even when build result is failure. Using jenkins UI I can access artifacts via http url JENKINS_URL/job/jobname/lastCompletedBuild/artifact/file.ext But I need to access this artifact directly from filesystem where artifacts are stored, in my case it is custom path: /mnt/jenkins/builds/jobname/lastCompletedBuild/archive/file.ext but lastCompletedBuild symlink is not created. I still can access the file, but I have to know build number. The same is for lastBuild. It works for lastCompletedBuild, lastUnstableBuild, lastFailedBuild, lastUnsuccessfulBuild. All short url from job page have their respective symlinks except lastCompletedBuild. Is it intentional?
[JIRA] (JENKINS-43540) builds/lastSuccessfulBuild symlink is not created
Title: Message Title Daniel Jeznach commented on JENKINS-43540 Re: builds/lastSuccessfulBuild symlink is not created I have similiar issue with no lastCompletedBuild, looks related. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55622) P4 plugin keeps triggering new build on the same change when polling enabled
Title: Message Title Daniel Jeznach created an issue Jenkins / JENKINS-55622 P4 plugin keeps triggering new build on the same change when polling enabled Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-01-16 14:26 Environment: Ubuntu 16.04.5 LTS (Xenial Xerus) openjdk version "1.8.0_181" p4 pluguin version: 1.9.5 Jenkins 2.138.3, run via: /usr/bin/daemon --name=jenkins.qata --inherit --env=JENKINS_HOME=/var/lib/jenkins/qata --output=/var/log/jenkins/jenkins.qata.log --pidfile=/var/run/jenkins/qata.pid -- /usr/lib/jvm/java-1.8.0-openjdk-amd64/jre/bin/java -Djava.awt.headless=true -Xmx2048m -Djava.net.preferIPv4Stack=true -Djcifs.smb.client.disablePlainTextPasswords=false -Dhudson.security.csrf.requestfield=Jenkins-Crumb -DsessionTimeout=1440 -Dhudson.model.DirectoryBrowserSupport.CSP=default-src 'self'; img-src 'self' data: *; style-src 'self' 'unsafe-inline'; child-src 'self'; frame-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; frame-ancestors 'self' -jar /var/lib/jenkins/qata/jenkins.war --httpPort=8996 --prefix=/qata -Xdebug jenkins+ 20411 1.7 4.6 8108212 1534816 ? Sl 2018 1404:00 \_ /usr/lib/jvm/java-1.8.0-openjdk-amd64/jre/bin/java -Djava.awt.headless=true -Xmx2048m -Djava.net.preferIPv4Stack=true -Djcifs.smb.client.disablePlainTextPasswords=false -Dhudson.security.csrf.requestfield=Jenkins-Crumb -DsessionTimeout=1440 -Dhudson.model.DirectoryBrowserSupport.CSP=default-src 'self'; img-src 'self' data: *; style-src 'self' 'unsafe-inline'; child-src 'self'; frame-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; frame-ancestors 'self' -jar /var/lib/jenkins/qata/jenkins.war --httpPort=8996 --prefix=/qata -Xdebug Priority: Minor Reporter: Daniel Jeznach I have a job configured to poll perforce @hourly. One build
[JIRA] (JENKINS-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title Daniel Jeznach closed an issue as Not A Defect Jenkins / JENKINS-55008 P4 Plugin generates ticket on slave that it does not use Change By: Daniel Jeznach Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title Daniel Jeznach commented on JENKINS-55008 Re: P4 Plugin generates ticket on slave that it does not use Hi, yes, I am able to login. Looks I was not aware this option is even there, but fortunately this solves my issue. Thank you. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-55008
P4 Plugin generates ticket on slave that it does not use
Change By:
Daniel Jeznach
I have job with configured P4 repository and following execute shell:{{env | grep -P '^P4'}}This job is executed on node js-qata-u16. I log into that node and log out of perforce:{{ {{ $ p4 logout}} }} {{User xbuild.qa logged out.}}Now I run jenkins job, which displays following data in log:{{ {{ + env}} }} {{+ grep -P ^P4}}{{P4_CLIENT=jenkins-js-qata-u16-p4test-0}}{{P4_TICKET=BA9C6CDCD5455D69DB94338D74729738}}{{P4_USER=xbuild.qa}}But on js-qata-u16 node I do:{{$ p4 tickets}}{{ {{ p4master.hh.imgtec.org:1666 (xbuild.qa) 84D5F61285DE96EF5EC6C5462EF10171}} }} This ticket is different. It looks like P4 plugin does p4 login on slave, but does not use generated ticket. In my opinion it should do p4 login -a on slave, so master and slaves use the same ticket. Currently, ticket generated after such operation is not used anywhere.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-55008
P4 Plugin generates ticket on slave that it does not use
Change By:
Daniel Jeznach
I have job with configured P4 repository and following execute shell:{{env | grep -P '^P4'}}This job is executed on node js-qata-u16. I log into that node and log out of perforce:{{$ p4 logout}}{{User xbuild.qa logged out.}}Now I run jenkins job, which displays following data in log:{{+ env}}{{+ grep -P ^P4}}{{P4_CLIENT=jenkins-js-qata-u16-p4test-0}}{{P4_TICKET=BA9C6CDCD5455D69DB94338D74729738}}{{P4_USER=xbuild.qa}}But on js-qata-u16 node I do:{{$ p4 tickets}}{{p4master .hh.imgtec.org :1666 (xbuild.qa) 84D5F61285DE96EF5EC6C5462EF10171}}This ticket is different. It looks like P4 plugin does p4 login on slave, but does not use generated ticket. In my opinion it should do p4 login -a on slave, so master and slaves use the same ticket. Currently, ticket generated after such operation is not used anywhere.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title
Daniel Jeznach updated an issue
Jenkins / JENKINS-55008
P4 Plugin generates ticket on slave that it does not use
Change By:
Daniel Jeznach
I have job with configured P4 repository and following execute shell:{{env | grep -P '^P4'}}This job is executed on node js-qata-u16. I log into that node and log out of perforce:{{ {{ $ p4 logout}} }} {{ User xbuild.qa logged out.}}Now I run jenkins job, which displays following data in log:{{ {{ + env}} }} {{ + grep -P ^P4}}{{ P4_CLIENT=jenkins-js-qata-u16-p4test-0}}{{ P4_TICKET=BA9C6CDCD5455D69DB94338D74729738}}{{ P4_USER=xbuild.qa}}But on js-qata-u16 node I do:{{$ p4 tickets }}{{ {{ p4master.hh.imgtec.org:1666 (xbuild.qa) 84D5F61285DE96EF5EC6C5462EF10171}} }} This ticket is different. It looks like P4 plugin does p4 login on slave, but does not use generated ticket. In my opinion it should do p4 login -a on slave, so master and slaves use the same ticket. Currently, ticket generated after such operation is not used anywhere.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-55008) P4 Plugin generates ticket on slave that it does not use
Title: Message Title
Daniel Jeznach created an issue
Jenkins / JENKINS-55008
P4 Plugin generates ticket on slave that it does not use
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-12-04 13:46
Priority:
Minor
Reporter:
Daniel Jeznach
I have job with configured P4 repository and following execute shell: env | grep -P '^P4' This job is executed on node js-qata-u16. I log into that node and log out of perforce: $ p4 logout {{ User xbuild.qa logged out.}} Now I run jenkins job, which displays following data in log: + env {{ + grep -P ^P4}} {{ P4_CLIENT=jenkins-js-qata-u16-p4test-0}} {{ P4_TICKET=BA9C6CDCD5455D69DB94338D74729738}} {{ P4_USER=xbuild.qa}} But on js-qata-u16 node I do: {{$ p4 tickets }} p4master.hh.imgtec.org:1666 (xbuild.qa) 84D5F61285DE96EF5EC6C5462EF10171 This ticket is different. It looks like P4 plugin does p4 login on slave, but does not use generated ticket. In my opinion it should do p4 login -a on slave, so master and slaves use the same ticket. Currently, ticket generated after such operation is not used anywhere.
Add Comment
