[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan I would need to test that. I can do that but it will be a couple of days due to other priorities. i changed the severity of this because saving the data is not the intended use case. i will update in a day of 2 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.205931.1587715343000.23107.1588839720235%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson updated an issue Jenkins / JENKINS-62040 pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan Change By: Marky Jackson Priority: Blocker Trivial 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.205931.1587715343000.23103.1588839600348%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson closed an issue as Cannot Reproduce Jenkins / JENKINS-62040 pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan Change By: Marky Jackson Status: In Progress Closed Resolution: Cannot Reproduce 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.205931.1587715343000.21428.1588644611179%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan The scan keeps a report of vulnerabilities and policy evaluations. This happens during each scan Clean up should always take place unless there was some edge case that stopped that from happening. Network latency, Jenkins hiccup, etc. Depending on how your scan job is configured, all jobs should retain the output of the report and there is a historical linkage in your workspace. Hope that helps 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.205931.1587715343000.20135.1588295820369%40Atlassian.JIRA.
[JIRA] (JENKINS-61980) Plugin Failed to load the Matrix
Title: Message Title Marky Jackson commented on JENKINS-61980 Re: Plugin Failed to load the Matrix Monil Patel I will take a look shortly 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.205870.1587423122000.20105.1588282380239%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan I will leave.this open in till Friday. I think the main answer is mine from yesterday. Let me know if I am misinterpreting 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.205931.1587715343000.19928.1588250640186%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan Tony Wen you are correct. A directory with all the vulnerability data is what you are referring to, in most cases you should not see that because of the clean up that takes place. In some edge cases, that clean up doesn't happen and that is why you see it. 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.205931.1587715343000.19754.1588213800326%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan My apologies for the delayed reply. I tried reproducing this and could not. In looking at your Jenkinsfile, I see that you are using a library, that could be suspect. Can you provide the logs from Managed Jenkins>System Logs 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.205931.1587715343000.18896.1588081020216%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan I will attempt to duplicate your setup later this AM 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.205931.1587715343000.17902.1587884700148%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan What version of Jenkins are you on? 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.205931.1587715343000.17858.1587876360201%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson started work on JENKINS-62040 Change By: Marky Jackson Status: Open In Progress 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.205931.1587715343000.17072.1587730141354%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Marky Jackson commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan Can you kindly share your jenkinsfile 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.205931.1587715343000.17069.1587730141240%40Atlassian.JIRA.
[JIRA] (JENKINS-61980) Plugin Failed to load the Matrix
Title: Message Title Marky Jackson commented on JENKINS-61980 Re: Plugin Failed to load the Matrix Can you share a screenshot of the config page in the Jenkins UI? Also, can you share you scrape config? 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.205870.1587423122000.14339.1587423360203%40Atlassian.JIRA.
[JIRA] (JENKINS-61837) Build new JNLP Image alternative use
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-61837 Build new JNLP Image alternative use Issue Type: Task Assignee: Marky Jackson Components: kubernetes-plugin Created: 2020-04-07 18:19 Priority: Minor Reporter: Marky Jackson There have been a few use cases where additional functionality is needed in the JNLP agent image. This is a side task for me to build out such an image and also document how to build out additional image functionality without messing with the JNLP remoting aspect. Please ping me if you have any questions. Add Comment
[JIRA] (JENKINS-61703) This is a test issue
Title: Message Title Marky Jackson updated JENKINS-61703 Jenkins / JENKINS-61703 This is a test issue Change By: Marky Jackson Status: Open Fixed but Unreleased Resolution: Fixed 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.205528.1585266046000.736.1585266300234%40Atlassian.JIRA.
[JIRA] (JENKINS-61703) This is a test issue
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-61703 This is a test issue Issue Type: Bug Assignee: Marky Jackson Components: anchore-container-scanner-plugin Created: 2020-03-26 23:40 Environment: This is a test issue Priority: Minor Reporter: Marky Jackson This is a test issue Add Comment
[JIRA] (JENKINS-61701) Prometheus plugin exports 0 builds on all slaves
Title: Message Title Marky Jackson commented on JENKINS-61701 Re: Prometheus plugin exports 0 builds on all slaves Most welcome 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.205526.1585255071000.717.1585255680218%40Atlassian.JIRA.
[JIRA] (JENKINS-61701) Prometheus plugin exports 0 builds on all slaves
Title: Message Title Marky Jackson commented on JENKINS-61701 Re: Prometheus plugin exports 0 builds on all slaves I have been planning on adding some more to this. I will add this to my upcoming roadmap 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.205526.1585255071000.712.1585255260247%40Atlassian.JIRA.
[JIRA] (JENKINS-61610) Request to help maintain Kubernetes-Plugin
Title: Message Title Marky Jackson updated JENKINS-61610 Opening an infra ticket Jenkins / JENKINS-61610 Request to help maintain Kubernetes-Plugin Change By: Marky Jackson Status: Open Fixed but Unreleased Resolution: Fixed 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/ms
[JIRA] (JENKINS-61610) Request to help maintain Kubernetes-Plugin
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-61610 Request to help maintain Kubernetes-Plugin Issue Type: Task Assignee: Unassigned Components: kubernetes-plugin Created: 2020-03-22 06:15 Priority: Minor Reporter: Marky Jackson Request to help maintain the Kubernetes-Plugin. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61413) Prometheus Plugin does not deliver Informations for a large Jenkins Installation.
Title: Message Title Marky Jackson commented on JENKINS-61413 Re: Prometheus Plugin does not deliver Informations for a large Jenkins Installation. You general Jenkins log output. Also if you can provide the Prometheus logs (depending on your os /var/lib/docker/containers//.log) 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.205073.1583849238000.3998.1583849760168%40Atlassian.JIRA.
[JIRA] (JENKINS-61413) Prometheus Plugin does not deliver Informations for a large Jenkins Installation.
Title: Message Title Marky Jackson commented on JENKINS-61413 Re: Prometheus Plugin does not deliver Informations for a large Jenkins Installation. Stephan Leiser Can you provide any logs/output? Also, can you provide the basic of your configuration (eg. Jenkins version & plugin version)? Thanks 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.205073.1583849238000.3990.1583849410766%40Atlassian.JIRA.
[JIRA] (JENKINS-61170) Document the basic setup of the Kubernetes Jenkins plugin
Title: Message Title Marky Jackson commented on JENKINS-61170 Re: Document the basic setup of the Kubernetes Jenkins plugin PR has been merged 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.204710.158222872.5014.1582478160449%40Atlassian.JIRA.
[JIRA] (JENKINS-61170) Document the basic setup of the Kubernetes Jenkins plugin
Title: Message Title Marky Jackson resolved as Fixed Jenkins / JENKINS-61170 Document the basic setup of the Kubernetes Jenkins plugin Change By: Marky Jackson Status: Open Resolved Resolution: Fixed 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.204710.158222872.5016.1582478160483%40Atlassian.JIRA.
[JIRA] (JENKINS-61170) Document the basic setup of the Kubernetes Jenkins plugin
Title: Message Title Marky Jackson commented on JENKINS-61170 Re: Document the basic setup of the Kubernetes Jenkins plugin PR: https://github.com/jenkinsci/kubernetes-plugin/pull/716 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.204710.158222872.3993.1582237020120%40Atlassian.JIRA.
[JIRA] (JENKINS-61170) Document the basic setup of the Kubernetes Jenkins plugin
Title: Message Title Marky Jackson commented on JENKINS-61170 Re: Document the basic setup of the Kubernetes Jenkins plugin A member of the community is concerned that the README.md does not detail the basic setup of this plugin. I am taking the initiative to document a straight forward configuration and will work with this community member to ensure they deem it acceptable. I will PR it once I am completed 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.204710.158222872.3884.1582228920198%40Atlassian.JIRA.
[JIRA] (JENKINS-61170) Document the basic setup of the Kubernetes Jenkins plugin
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-61170 Document the basic setup of the Kubernetes Jenkins plugin Issue Type: Task Assignee: Marky Jackson Components: kubernetes-plugin Created: 2020-02-20 19:58 Priority: Minor Reporter: Marky Jackson 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 Googl
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Devin Nusbaum at this point it appears someone upgraded a plugin which in turn upgraded 1.29 to 1.33 and that broke all the dependancies. I moved everything back to native docker calls as Jesse Glick alluded to 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.203277.1574777832000.795.1575491340151%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile I did a restart Devin Nusbaum. I did also just try running it in the script console 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.203277.1574777832000.7325.1574787780698%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Devin Nusbaum formatting is not working for some reason. Jesse Glick I totally know this feeling 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.203277.1574777832000.7314.1574786700242%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile ?? I would not recommend using agent docker (or agent dockerfile). These ultimately rely on the withDockerContainer step and rather complex injection of docker exec into commands, which can easily break when there are issues with volume mounts and so on. Much safer and more transparent to use a plain label and run CLI docker commands (build, run) from sh.?? Oh that is painful given our online documentation almost seems to promote the containerized approach (i.e. https://jenkins.io/doc/book/pipeline/docker/) 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.203277.1574777832000.7293.1574785560167%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title
Marky Jackson commented on JENKINS-60286
Re: durable-task v1.33 fails with agent Dockerfile
Devin Nusbaum here is the build log from the console. I eventually have to hard kill the job because it just hangs at the missing file:
Started by user mark.jack...@sysdig.com 15:51:39 Connecting to https://api.github.com using xxx/** (z) Obtained Jenkinsfile from xxx Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] node Running on EC2 (ec2) - ${WORKER_NAME} (ec2ID) in /home/${USER}/workspace/ntend-pipeline_customer-settings [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Checkout SCM) [Pipeline] checkout using credential ${TOKEN} Cloning the remote Git repository Cloning repository ${REPO} > git init /home/${USER}/workspace/ntend-pipeline_customer-settings # timeout=10 } Fetching upstream changes from ${REPO} > git --version # timeout=10 } using GIT_SSH to set credentials ${TOKEN} > git fetch --tags --progress -- ${REPO} +refs/heads/*:refs/remotes/origin/* # timeout=10 } Checking out Revision ${REVISION} (customer-settings) Commit message: "Reverting my changes" > git config remote.origin.url ${REPO} # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url ${REPO} # timeout=10 Fetching upstream changes from ${REPO} using GIT_SSH to set credentials ${TOKEN} > git fetch --tags --progress --${REPO} +refs/heads/customer-settings:refs/remotes/origin/customer-settings # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f ${REVISION} # timeout=10 > git rev-list --no-walk ${REVISION} # timeout=10 [Pipeline] } [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Agent Setup) [Pipeline] isUnix [Pipeline] readFile [Pipeline] sh + docker build -t c7c9f201c0dbb37091ac75c689812beae3bf54b4 -f Dockerfile . WARNING: Error loading config file: /home/${USER}/.docker/config.json: EOF Sending build context to Docker daemon 116.3MBStep 1/13 : FROM ubuntu:latest ---> 775349758637 Step 2/13 : ENV DEBIAN_FRONTEND=noninteractive ---> Using cache ---> 08bb415b8561 Step 3/13 : RUN apt-get update -y && apt-get install apt-transport-https ca-certificates curl gnupg git python-pip python2.7 python2.7-dev groff-base build-essential parallel jq grep awscli -y --no-install-recommends ---> Using cache ---> 2d2f267ee29f Step 4/13 : RUN groupadd ${USER} -g 500 ---> Using cache ---> c1508155cdc1 Step 5/13 : RUN useradd -m -d /home/${USER} -g ${USER} -u 500 ${USER} ---> Using cache ---> 12ad008b1a8a Step 6/13 : RUN curl -sSL https://dl.google.com/linux/linux_signing_key.pub | apt-key add - && echo "deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main" > /etc/apt/sources.list.d/google-chrome.list ---> Using cache ---> 1e4d342560b2 Step 7/13 : RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - ---> Using cache ---> 7ae11025dc8e Step 8/13 : RUN echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list ---> Using cache ---> 6f40d90e286a Step 9/13 : ENV YARN_VERSION=1.17.3-1 ---> Using cache ---> 818b40b458e3 Step 10/13 : RUN apt-get update && apt-get install -y yarn=$YARN_VERSION --no-install-recommends ---> Using cache ---> 88de9a37077f Step 11/13 : RUN apt-get update && apt-get install -y google-chrome-stable ---> Using cache ---> f57b038effc4 Step 12/13 : ENV NODE_VERSION=10.16.3 ---> Using cache
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile The 2nd above stack trace is with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true turned on and doesn't show anything new 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.203277.1574777832000.7258.1574782800149%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile JENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[16:sh]:Owner[monitor-frontend-pipeline/customer-settings/34:monitor-frontend-pipeline/customer-settings #34] Nov 26, 2019 3:32:04 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunching task against hudson.remoting.Channel@13b6e486:EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) using RemoteLauncher[hudson.remoting.Channel@13b6e486:EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5)] Nov 26, 2019 3:32:04 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunched task Nov 26, 2019 3:32:04 PM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepEC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) seems to be online so using /home/ec2-user/workspace/ntend-pipeline_customer-settings Nov 26, 2019 3:32:04 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepcreating filtered stream Nov 26, 2019 3:32:04 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepstill running in /home/ec2-user/workspace/ntend-pipeline_customer-settings on EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) Nov 26, 2019 3:32:04 PM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepEC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) seems to be online so using /home/ec2-user/workspace/ntend-pipeline_customer-settings Nov 26, 2019 3:32:04 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepstill running in /home/ec2-user/workspace/ntend-pipeline_customer-settings on EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) Nov 26, 2019 3:32:05 PM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepEC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) seems to be online so using /home/ec2-user/workspace/ntend-pipeline_customer-settings Nov 26, 2019 3:32:05 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepcalling close with nl=true Nov 26, 2019 3:32:06 PM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepJENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[20:sh]:Owner[monitor-frontend-pipeline/customer-settings/34:monitor-frontend-pipeline/customer-settings #34] Nov 26, 2019 3:32:06 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunching task against hudson.remoting.Channel@13b6e486:EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) using RemoteLauncher[hudson.remoting.Channel@13b6e486:EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5)] Nov 26, 2019 3:32:06 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunched task Nov 26, 2019 3:32:07 PM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepEC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) seems to be online so using /home/ec2-user/workspace/ntend-pipeline_customer-settings Nov 26, 2019 3:32:07 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepcreating filtered stream Nov 26, 2019 3:32:07 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepcalling close with nl=true Nov 26, 2019 3:32:08 PM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepJENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[25:sh]:Owne
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Was this working for you previously? If so, what plugin versions have been installed/upgraded since then? Yes it was on version 1.29 for durable task and core code Jenkins version 2.190.2 Does it happen consistently or intermittently? It happens consistently for jobs that have the agent set to use Dockerfiles but no other jobs types Did you try adding -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true as indicated to your Jenkins Java startup settings to see if you get more detailed error information? I will add that now Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received t
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile Here is the stack trace from the logs: Nov 26, 2019 3:17:48 PM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepEC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) seems to be online so using /home/ec2-user/workspace/ntend-pipeline_customer-settings@3 Nov 26, 2019 3:17:48 PM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepcould not check /home/ec2-user/workspace/ntend-pipeline_customer-settings@3 Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.FilePath.act(FilePath.java:1072) at hudson.FilePath.act(FilePath.java:1061) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.getOutput(FileMonitoringTask.java:300) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.getOutput(FileMonitoringTask.java:293) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.lambda$check$3(DurableTaskStep.java:604) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.handleExit(DurableTaskStep.java:651) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:604) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:548) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.io.FileNotFoundException: File '/home/ec2-user/workspace/ntend-pipeline_customer-settings@3@tmp/durable-a112d9e1/output.txt' does not exist at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:297) at org.apache.commons.io.FileUtils.readFileToByteArray(FileUtils.java:1851) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1.invoke(FileMonitoringTask.java:302) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController$1.invoke(FileMonitoringTask.java:300) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748)
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson commented on JENKINS-60286 Re: durable-task v1.33 fails with agent Dockerfile I eventually have to hard kill the job. I tried all applicable workarounds including all noted in previous tickets as workaround to no avail. 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.203277.1574777832000.7181.1574778420775%40Atlassian.JIRA.
[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-60286 durable-task v1.33 fails with agent Dockerfile Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2019-11-26 14:17 Environment: Jenkins version 2.190.3 Priority: Blocker Reporter: Marky Jackson Error I get process apparently never started in /home/ec2-user/workspace/ntend-pipeline_customer-settings@3@tmp/durable-f026a6cb (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer) Cannot contact EC2 (ec2) - new-builder-backend-j8 (i-0d91350838c6340f5): java.io.FileNotFoundException: File '/home/ec2-user/workspace/ntend-pipeline_customer-settings@3@tmp/durable-f026a6cb/output.txt' does not existHard kill! Add Comment
[JIRA] (JENKINS-59675) Upgrading to 2.0.6 is causing UI issues in pipelines
Title: Message Title Marky Jackson commented on JENKINS-59675 Re: Upgrading to 2.0.6 is causing UI issues in pipelines Thank you for reporting this and in such great details Naresh Rayapati. I will try and reproduce based on the steps you provided. I will do so based on your version of Jenkins and also the LTS version which the latest release code was built off of. Give me a day 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.202368.1570259911000.1548.1570292160232%40Atlassian.JIRA.
[JIRA] (JENKINS-59537) Test open PR's
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59537 Test open PR's Issue Type: Task Assignee: Marky Jackson Components: prometheus-plugin Created: 2019-09-26 01:23 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59536) Triage open issues
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59536 Triage open issues Issue Type: Task Assignee: Marky Jackson Components: prometheus-plugin Created: 2019-09-26 01:22 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59535) Document setting up development environment for the plugin
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59535 Document setting up development environment for the plugin Issue Type: Task Assignee: Marky Jackson Components: prometheus-plugin Created: 2019-09-26 01:22 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59534) Document setting up the plugin and use cases
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59534 Document setting up the plugin and use cases Issue Type: Task Assignee: Marky Jackson Components: prometheus-plugin Created: 2019-09-26 01:21 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59533) Document setting up development environment for the plugin
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59533 Document setting up development environment for the plugin Issue Type: Task Assignee: Marky Jackson Components: gitlab-plugin Created: 2019-09-26 01:21 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59532) Document the setup to use the plugin for the wiki
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59532 Document the setup to use the plugin for the wiki Issue Type: Task Assignee: Marky Jackson Components: gitlab-plugin Created: 2019-09-26 01:20 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59531) Triage all open issues
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59531 Triage all open issues Issue Type: Task Assignee: Marky Jackson Components: gitlab-plugin Created: 2019-09-26 01:19 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59530) Manually test all open PR's
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59530 Manually test all open PR's Issue Type: Task Assignee: Marky Jackson Components: gitlab-plugin Created: 2019-09-26 01:19 Labels: newbie-friendly Priority: Minor Reporter: Marky Jackson Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59289) Go through open Github PR for plugin
Title: Message Title Marky Jackson commented on JENKINS-59289 Re: Go through open Github PR for plugin Left off on Support user regex filter for note trigger #923 opened on May 1 by the-sea Need to eat. Will pick up tomorrow 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.201833.1568078431000.375.1568080020121%40Atlassian.JIRA.
[JIRA] (JENKINS-59289) Go through open Github PR for plugin
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59289 Go through open Github PR for plugin Issue Type: Task Assignee: Marky Jackson Components: gitlab-plugin Created: 2019-09-10 01:20 Priority: Minor Reporter: Marky Jackson What I am trying to ascertain from current open pr's is ``` Is there an associated Github issue with this PR? What about a Jenkins jira? If so, can you link them? If not, can you open them and note this PR? Thank you for that. I am coming onboard as a maintainer and link to make sure we keep as much details across the Jenkins spectrum as well. Thanks again ``` Add Comment
[JIRA] (JENKINS-59289) Go through open Github PR for plugin
Title: Message Title Marky Jackson started work on JENKINS-59289 Change By: Marky Jackson Status: Open In Progress 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.201833.1568078431000.373.1568078460359%40Atlassian.JIRA.
[JIRA] (JENKINS-59273) Known security vulnerabilities
Title: Message Title Marky Jackson commented on JENKINS-59273 Re: Known security vulnerabilities PR has been merged 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.201773.1567956187000.367.1568078040442%40Atlassian.JIRA.
[JIRA] (JENKINS-59273) Known security vulnerabilities
Title: Message Title Marky Jackson resolved as Fixed Jenkins / JENKINS-59273 Known security vulnerabilities Change By: Marky Jackson Status: In Progress Resolved Resolution: Fixed 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.201773.1567956187000.369.1568078040686%40Atlassian.JIRA.
[JIRA] (JENKINS-59273) Known security vulnerabilities
Title: Message Title Marky Jackson started work on JENKINS-59273 Change By: Marky Jackson Status: Open In Progress 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.201773.1567956187000.8750.1567966560265%40Atlassian.JIRA.
[JIRA] (JENKINS-59273) Known security vulnerabilities
Title: Message Title Marky Jackson commented on JENKINS-59273 Re: Known security vulnerabilities Github issue: https://github.com/jenkinsci/gitlab-plugin/issues/971 Github PR: https://github.com/jenkinsci/gitlab-plugin/pull/972 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.201773.1567956187000.8735.1567956540147%40Atlassian.JIRA.
[JIRA] (JENKINS-59273) Known security vulnerabilities
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59273 Known security vulnerabilities Issue Type: Patch Assignee: Marky Jackson Components: gitlab-plugin Created: 2019-09-08 15:23 Priority: Major Reporter: Marky Jackson org.apache.httpcomponents:httpclient security CVE-2014-3577 More information com.fasterxml.jackson.core:jackson-databind security CVE-2019-14379 More information Add Comment
[JIRA] (JENKINS-59269) adding upload perms for jequals5
Title: Message Title Marky Jackson commented on JENKINS-59269 Re: adding upload perms for jequals5 code merged 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.201768.156786948.8641.1567895640405%40Atlassian.JIRA.
[JIRA] (JENKINS-59269) adding upload perms for jequals5
Title: Message Title Marky Jackson resolved as Fixed Jenkins / JENKINS-59269 adding upload perms for jequals5 Change By: Marky Jackson Status: In Progress Resolved Resolution: Fixed 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.201768.156786948.8643.1567895640431%40Atlassian.JIRA.
[JIRA] (JENKINS-59269) adding upload perms for jequals5
Title: Message Title Marky Jackson started work on JENKINS-59269 Change By: Marky Jackson Status: Open In Progress 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.201768.156786948.8613.1567874160211%40Atlassian.JIRA.
[JIRA] (JENKINS-59269) adding upload perms for jequals5
Title: Message Title Marky Jackson commented on JENKINS-59269 Re: adding upload perms for jequals5 repo issue tracking: https://github.com/jenkinsci/gitlab-plugin/issues/970 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.201768.156786948.8611.1567869960143%40Atlassian.JIRA.
[JIRA] (JENKINS-59269) adding upload perms for jequals5
Title: Message Title Marky Jackson commented on JENKINS-59269 Re: adding upload perms for jequals5 https://github.com/jenkins-infra/repository-permissions-updater/pull/1272 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.201768.156786948.8609.1567869780201%40Atlassian.JIRA.
[JIRA] (JENKINS-59269) adding upload perms for jequals5
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-59269 adding upload perms for jequals5 Issue Type: Task Assignee: Marky Jackson Components: gitlab-plugin Created: 2019-09-07 15:18 Priority: Minor Reporter: Marky Jackson 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.201768.156786948.8607.1567869540300%40Atlassian.JIRA.
[JIRA] (JENKINS-58829) Add symbols to SCM discovery traits to prevent name clashes
Title: Message Title Marky Jackson updated an issue Jenkins / JENKINS-58829 Add symbols to SCM discovery traits to prevent name clashes Change By: Marky Jackson Labels: gsoc-2019 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.201142.1565100831000.8941.1565104380293%40Atlassian.JIRA.
[JIRA] (JENKINS-58445) Decide on GitLab Pipeline status notifier strategy
Title: Message Title Marky Jackson commented on JENKINS-58445 Re: Decide on GitLab Pipeline status notifier strategy I agree. Overall pipeline status is much easier but will also leave that up to Parichay Barpanda 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.200577.1562856316000.14108.1563371700127%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58271) Run Book Style Documentation for Plugin
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-58271 Run Book Style Documentation for Plugin Issue Type: Improvement Assignee: Marky Jackson Components: prometheus-plugin Created: 2019-06-30 16:22 Labels: plugin Priority: Minor Reporter: Marky Jackson Run Book Style Documentation for Plugin and update wiki Add Comment
[JIRA] (JENKINS-58247) Fix link to Jenkins dockerhub for plugin
Title: Message Title Marky Jackson resolved as Fixed Jenkins / JENKINS-58247 Fix link to Jenkins dockerhub for plugin Change By: Marky Jackson Status: In Progress Resolved Resolution: Fixed 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.200310.156169730.11670.1561723980342%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58247) Fix link to Jenkins dockerhub for plugin
Title: Message Title Marky Jackson commented on JENKINS-58247 Re: Fix link to Jenkins dockerhub for plugin Code has been merged and this will go in to the next release 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.200310.156169730.11668.1561723920143%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49222) Summaries doesn't contain _sum metrics
Title: Message Title Marky Jackson stopped work on JENKINS-49222 Change By: Marky Jackson Status: In Progress Open 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.188064.1517215041000.11164.1561697400277%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58247) Fix link to Jenkins dockerhub for plugin
Title: Message Title Marky Jackson commented on JENKINS-58247 Re: Fix link to Jenkins dockerhub for plugin PR awaiting approval: https://github.com/jenkinsci/amazon-ecs-plugin/pull/112 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.200310.156169730.11161.1561697340826%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58247) Fix link to Jenkins dockerhub for plugin
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-58247 Fix link to Jenkins dockerhub for plugin Issue Type: Bug Assignee: Marky Jackson Components: amazon-ecs-plugin Created: 2019-06-28 04:48 Priority: Minor Reporter: Marky Jackson Fix links to dockerhub. Currently references jenkinsci/jnlp-slave but should be jenkins/jnlp-slave Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58247) Fix link to Jenkins dockerhub for plugin
Title: Message Title Marky Jackson started work on JENKINS-58247 Change By: Marky Jackson Status: Open In Progress 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.200310.156169730.11159.1561697340696%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58246) Better setup and runbook style documentation for this plugin
Title: Message Title Marky Jackson commented on JENKINS-58246 Re: Better setup and runbook style documentation for this plugin Link to GitHub repo issues I created for this: https://github.com/jenkinsci/prometheus-plugin/issues/113 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.200309.1561697059000.11155.1561697160112%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58246) Better setup and runbook style documentation for this plugin
Title: Message Title Marky Jackson updated an issue Jenkins / JENKINS-58246 Better setup and runbook style documentation for this plugin Change By: Marky Jackson Summary: Better setup and runback runbook style documentation for this plugin 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.200309.1561697059000.11153.1561697100309%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58246) Better setup and runback style documentation for this plugin
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-58246 Better setup and runback style documentation for this plugin Issue Type: Improvement Assignee: Marky Jackson Components: prometheus-plugin Created: 2019-06-28 04:44 Priority: Minor Reporter: Marky Jackson As a plugin maintainer, I need to create better setup and runbook style documentation that will live on the wiki. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58204) Closing out coding phase 1
Title: Message Title Marky Jackson updated JENKINS-58204 This officially closes out coding phase 1 Jenkins / JENKINS-58204 Closing out coding phase 1 Change By: Marky Jackson Status: In Review Resolved Resolution: Done 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.200262.1561534963000.10189.1561596360300%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58204) Closing out coding phase 1
Title: Message Title Marky Jackson commented on JENKINS-58204 Re: Closing out coding phase 1 Awesome job @baymac, this officially closes out phase 1 coding 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.200262.1561534963000.9240.1561543680432%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57886) Add JCasC config test
Title: Message Title Marky Jackson updated JENKINS-57886 Jenkins / JENKINS-57886 Add JCasC config test Change By: Marky Jackson Status: In Review Progress 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.199850.1559832725000.23655.1559920020568%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57803) Add README to GitHub repository
Title: Message Title Marky Jackson started work on JENKINS-57803 Change By: Marky Jackson Status: Open In Progress 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.199754.1559329605000.23652.1559919900598%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57760) Add support for webhooks management
Title: Message Title Marky Jackson started work on JENKINS-57760 Change By: Marky Jackson Status: Open In Progress 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.199706.1559207961000.23650.1559919900575%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57539) Prepare design document for a top level architecture
Title: Message Title Marky Jackson commented on JENKINS-57539 Re: Prepare design document for a top level architecture Per team agreeable, this document is meeting acceptance. Parichay Barpanda says he would like to add a few more items to this body of work. I will leave open until then but it is agreed that this can be closed once that is done. 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.199447.1558177073000.17129.1559273580120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57770) For the life of me cannot get this to work
Title: Message Title Marky Jackson closed an issue as Incomplete I think I found my error Jenkins / JENKINS-57770 For the life of me cannot get this to work Change By: Marky Jackson Status: Open Closed Resolution: Incomplete 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.199717.1559251055000.17030.1559254201720%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57770) For the life of me cannot get this to work
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-57770 For the life of me cannot get this to work Issue Type: Bug Assignee: Carlos Sanchez Attachments: log.rtfd.zip Components: kubernetes-plugin Created: 2019-05-30 21:17 Labels: kuberenetes-plugin Priority: Minor Reporter: Marky Jackson I have a very vanilla setup using kops on AWS. I also have a super simple job that just executes a shell and sleeps for 5 No matter what I try the agent always fails. I have searched old tickets, google and asked around to no avail. Any help is greatly appreciated This is what the pods look like and the logs are attached: NAME READY STATUS RESTARTS AGE jenkins-7c94bc6dc8-dlx5q 1/1 Running 0 17h worker-2qpq5 0/2 Pending 0 0s worker-2qpq5 0/2 Pending 0 0s worker-2qpq5 0/2 ContainerCreating 0 0s worker-2qpq5 1/2 Error 0 2s worker-cpnww 0/2 Pending 0 0s worker-cpnww 0/2 Pending 0 0s worker-cpnww 0/2 ContainerCreating 0 0s worker-cpnww 2/2 Running 0 2s worker-cpnww 1/2 Error 0 3s worker-hkgbx 0/2 Pending 0 0s worker-hkgbx 0/2 Pending 0 0s worker-hkgbx 0/2 ContainerCreating 0 0s worker-hkgbx
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Marky Jackson updated JENKINS-57677 Student has completed this task Jenkins / JENKINS-57677 Create new repo for GSoC gitlab-branch-source-plugin Change By: Marky Jackson Status: Open Fixed but Unreleased Resolution: Fixed 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.199610.1558727311000.15315.1559144220315%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Marky Jackson commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin Parichay Barpanda since you created the repo, I would say this task is completed 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.199610.1558727311000.15306.1559143980200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Marky Jackson commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin I have sent an email to the Jenkins-dev mailing list here: https://groups.google.com/forum/#!topic/jenkinsci-dev/k_12IoFRNHg 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.199610.1558727311000.11931.1558795200184%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Marky Jackson commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin Parichay Barpanda Oleg Nenashev I think in the interest of time we should just use the current plugin GitHub repo (https://github.com/jenkinsci/gitlab-branch-source-plugin). So we will need to request access to this by becoming the maintainers, is that correct Oleg Nenashev and to do so we will need to request that through the jenkins-dev mailing? If so, I fear that the usual time it takes for the to happen can be lengthily, is there something we can do to expedite that faster Oleg Nenashev 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.199610.1558727311000.11925.1558794300175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title Marky Jackson commented on JENKINS-57677 Re: Create new repo for GSoC gitlab-branch-source-plugin Please add me as an admin of the repo 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.199610.1558727311000.11758.1558727580239%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57677) Create new repo for GSoC gitlab-branch-source-plugin
Title: Message Title
Marky Jackson created an issue
Jenkins / JENKINS-57677
Create new repo for GSoC gitlab-branch-source-plugin
Issue Type:
Task
Assignee:
Oleg Nenashev
Components:
gitlab-branch-source-plugin
Created:
2019-05-24 19:48
Priority:
Minor
Reporter:
Marky Jackson
For the GSoC project gitlab-branch-source-plugin the student is requesting a new repo be created titled "gitlab-branch-plugin Detailed reasoning for this is here: 2) I read the documentation of SCM API}}and {{Branch API Plugins to understand the classes needs to be implemented in GitLab Branch Source Plugin. Based on which I prepared the design document. This design document will be improved throughout the course of development. Will add apis, workflow, issues etc to it. 3) I have been studing the codebases of ArgelBargel's GitLab Branch Source Plugin, GitHub Branch Source Plugin}}and {{Gitea Plugin. My takeaway was GitLab BS has been implemented in a way that is not very different from the other Branch Source Plugins in terms of the underlying APIs implementation but still exists some differences that cannot be ignored. For example, i) The class names are different and many code refractories has been done so it creates a difficulty in implementing the same logic while extending the plugin. Like SCMSource has been broken down to other sub classes , SCMHeadCategory has some different implementation, SCMFileSystem is not implemented, APIs implementation also needs to be changed and the list goes on.. ii) The conclusion I have come to is that it would be rather lesser amount of work for me if I had to implement a new GitLab Branch Source Plugin which will be heavily inspired from Gitea Plugin (as suggested by Robert Sandall in mailing list) and also some inspiration will be taken from GitLab Branch Source and GitHub Branch Source Plugins. iii) I will send my compelete list of reasons not to develop the existing GitLab Branch Source Plugin.
[JIRA] (JENKINS-57662) A blog post about our project workflow
Title: Message Title Marky Jackson commented on JENKINS-57662 Re: A blog post about our project workflow Parichay Barpanda I agree with this flow and the entire blog post. Let's wait for Rick to also review 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.199595.1558706565000.11512.1558707360171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49222) Summaries doesn't contain _sum metrics
Title: Message Title Marky Jackson updated JENKINS-49222 Jenkins / JENKINS-49222 Summaries doesn't contain _sum metrics Change By: Marky Jackson Status: In Review Progress 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.188064.1517215041000.10614.1558638120238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49222) Summaries doesn't contain _sum metrics
Title: Message Title Marky Jackson commented on JENKINS-49222 Re: Summaries doesn't contain _sum metrics Alex Simenduev Thank you for responding. I will start looking in to this deeper 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.188064.1517215041000.10611.1558638060155%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44947) NPE for jenkins.queue values
Title: Message Title Marky Jackson assigned an issue to Unassigned Jenkins / JENKINS-44947 NPE for jenkins.queue values Change By: Marky Jackson Assignee: Marky Jackson 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.183022.1497629761000.10437.1558629660331%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49222) Summaries doesn't contain _sum metrics
Title: Message Title Marky Jackson started work on JENKINS-49222 Change By: Marky Jackson Status: Open In Progress 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.188064.1517215041000.10431.1558629540455%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49222) Summaries doesn't contain _sum metrics
Title: Message Title Marky Jackson commented on JENKINS-49222 Re: Summaries doesn't contain _sum metrics Can you advise Alex Simenduev if this is still an issue. Please also upgrade to the latest version 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.188064.1517215041000.10428.1558629540349%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49222) Summaries doesn't contain _sum metrics
Title: Message Title Marky Jackson updated JENKINS-49222 Jenkins / JENKINS-49222 Summaries doesn't contain _sum metrics Change By: Marky Jackson Status: In Progress Review 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.188064.1517215041000.10434.1558629540493%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44259) Jenkins is hanged due to plugin prometheus
Title: Message Title Marky Jackson resolved as Not A Defect Jenkins / JENKINS-44259 Jenkins is hanged due to plugin prometheus Change By: Marky Jackson Status: Open Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181941.1494740159000.10414.1558629480708%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44513) Request to GET /prometheus takes a huge amount of time (and memory)
Title: Message Title Marky Jackson commented on JENKINS-44513 Re: Request to GET /prometheus takes a huge amount of time (and memory) This should be resolved with latest update. Please upgrade 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.182353.149580649.10420.1558629480784%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44513) Request to GET /prometheus takes a huge amount of time (and memory)
Title: Message Title Marky Jackson resolved as Not A Defect Jenkins / JENKINS-44513 Request to GET /prometheus takes a huge amount of time (and memory) Change By: Marky Jackson Status: Open Resolved 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182353.149580649.10424.1558629480818%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44259) Jenkins is hanged due to plugin prometheus
Title: Message Title Marky Jackson commented on JENKINS-44259 Re: Jenkins is hanged due to plugin prometheus This should be resolved with latest update. Please give that a try 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.181941.1494740159000.10408.1558629420268%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Marky Jackson commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN I’m syncing with the plugin maintainer in an effort to ensure what I think is the root cause is mutual and the best way forward. Given this plugin has wide adoption, it is always best to ensure there is a uniformed approach 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Marky Jackson commented on JENKINS-55392 Re: java.util.concurrent.RejectedExecutionException AGAIN Ok, let me reproduce this 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.
