[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Timo Sand commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification Use case: We have a single job which does PR deployments. It is triggered by each PR's own build job, but with different params, like which branch to deploy etc. We would like to ensure that only the latest build gets deployed as it would be unnecessary to deploy older builds. Milestones and inverse locks seemed to offer a great solution to this, but milestones don't take parameters into account at all and thus it cancels jobs which have different parameters. 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.187125.1513079616000.14659.1587466020265%40Atlassian.JIRA.
[JIRA] (JENKINS-60959) Plugin runs only one agent pod per kubernetes node
Title: Message Title Timo Sand updated JENKINS-60959 Turns out we did have a misconfiguration where some of our agents were using a lot more resources than other Jenkins / JENKINS-60959 Plugin runs only one agent pod per kubernetes node Change By: Timo Sand Status: Open Fixed but Unreleased Resolution: Not A Defect 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
[JIRA] (JENKINS-60959) Plugin runs only one agent pod per kubernetes node
Title: Message Title Timo Sand created an issue Jenkins / JENKINS-60959 Plugin runs only one agent pod per kubernetes node Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2020-02-04 11:24 Environment: Jenkins ver. 2.204.2 plugin version 1.23.2 Priority: Minor Reporter: Timo Sand We are running kubernetes on EKS in AWS and are using fairly beefy machines for the nodes which Jenkins uses as agents. A podTemplate for our agents requests roughly a third of the resources of a k8s node, but still we only have 1 agent pod per k8s node. Is it possible we have a misconfiguration somewhere or is there a bug in how the NodeProvisioner works? Add Comment
[JIRA] (JENKINS-55705) Display link to downstream job in Blue Ocean
Title: Message Title Timo Sand commented on JENKINS-55705 Re: Display link to downstream job in Blue Ocean This seems to actually work now. But it only appears once the job is out pf the job queue 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.196898.1548078808000.1986.1578049140049%40Atlassian.JIRA.
[JIRA] (JENKINS-53912) Unable to use SSHCheckoutTrait
Title: Message Title
Timo Sand commented on JENKINS-53912
Re: Unable to use SSHCheckoutTrait
I found a workaround, but it's Ugly as hell.
organizationFolder('...') {
organizations {
...
}
orphanedItemStrategy {
...
}
triggers {
...
}
configure {
def traits = it / navigators / 'org.jenkinsci.plugins.github__branch__source.GitHubSCMNavigator' / traits
traits << "org.jenkinsci.plugins.github__branch__source.SSHCheckoutTrait" {
credentialsId('...')
}
traits << 'org.jenkinsci.plugins.github_branch_source.OriginPullRequestDiscoveryTrait' {
strategyId 1
}
}
}
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.194446.1538670788000.4261.1561018440139%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53912) Unable to use SSHCheckoutTrait
Title: Message Title
Timo Sand commented on JENKINS-53912
Re: Unable to use SSHCheckoutTrait
Liam Newman The same issue with trying to use { { originPullRequestDiscoveryTrait } }
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.194446.1538670788000.3427.1560955021478%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53912) Unable to use SSHCheckoutTrait
Title: Message Title
Timo Sand edited a comment on JENKINS-53912
Re: Unable to use SSHCheckoutTrait
[~bitwiseman] The same issue with trying to use \ { { code:java} originPullRequestDiscoveryTrait {code } }
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.194446.1538670788000.3429.1560955021751%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53912) Unable to use SSHCheckoutTrait
Title: Message Title Timo Sand commented on JENKINS-53912 Re: Unable to use SSHCheckoutTrait Liam Newman Yes 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.194446.1538670788000.2836.1560891180195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53912) Unable to use SSHCheckoutTrait
Title: Message Title Timo Sand commented on JENKINS-53912 Re: Unable to use SSHCheckoutTrait I have the same issue, any knowledge of how to circumvent? 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.194446.1538670788000.2370.1560857760228%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57375) Builds based on Jenkinsfiles do not report pending state to GitHub when queued
Title: Message Title Timo Sand created an issue Jenkins / JENKINS-57375 Builds based on Jenkinsfiles do not report pending state to GitHub when queued Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2019-05-08 15:12 Priority: Major Reporter: Timo Sand We have a 'Github Organization' project, which creates jobs for all repos if they have a Jenkinsfile available. We're having the problem in all of our repos that if a job is queued it does not change the github status to pending. We would expect it to be able to do this. Add Comment
[JIRA] (JENKINS-55705) Display link to downstream job in Blue Ocean
Title: Message Title Timo Sand created an issue Jenkins / JENKINS-55705 Display link to downstream job in Blue Ocean Issue Type: New Feature Assignee: Unassigned Components: pipeline-build-step-plugin Created: 2019-01-21 13:53 Priority: Minor Reporter: Timo Sand It would be really useful if the output included a link to the downstream job in Blue Ocean instead of the textual representation to the job. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55266) Add possibility to pass in commands for workspace cleanup
Title: Message Title
Timo Sand created an issue
Jenkins / JENKINS-55266
Add possibility to pass in commands for workspace cleanup
Issue Type:
New Feature
Assignee:
Oliver Gondža
Components:
ws-cleanup-plugin
Created:
2018-12-19 16:28
Priority:
Minor
Reporter:
Timo Sand
We run everything with `docker-compose` in our Jobs and we have to add a `docker-compose down` to the end of each stage, which takes unnecessary time from the jobs completion. It would be great if we could add a closure to `cleanWs` in order to run some commands deferredly at the end of the build
cleanWs() {
docker-compose -f docker-compose.ci.yml down --volumes --remove-orphans
}
Add Comment
[JIRA] (JENKINS-55265) Unsuccessful post stage fires even on Success status
Title: Message Title Timo Sand created an issue Jenkins / JENKINS-55265 Unsuccessful post stage fires even on Success status Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2018-12-19 16:23 Priority: Minor Reporter: Timo Sand I tried adding an `unsuccessful` block to my post stage today, but instead of working like it should it first ran everything from the `success` block and then from the `unsuccessful` block Add Comment This message was sent by
[JIRA] (JENKINS-44304) node build history is missing REST API
Title: Message Title Timo Sand commented on JENKINS-44304 Re: node build history is missing REST API The RSS feed only has information on jobs specifically assigned to nodes, but if the node just runs whatever, then the RSS feed is empty. Is there any other way to programatically access this data from an API? 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-22794) Option to remove from log: "Seen branch in repository blah blah blah"
Title: Message Title Timo Sand commented on JENKINS-22794 Re: Option to remove from log: "Seen branch in repository blah blah blah" Does this actually work anymore? I've set this on master, but it doesn't seem to work. Looking at the GitClient code, it should work, but... 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-49105) Can't send data to influx
Title: Message Title Timo Sand commented on JENKINS-49105 Re: Can't send data to influx Aleksi Simell Yet that does not explain why the target object has been preparsed and thus passed in the wrong format to the constructor. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49105) Can't send data to influx
Title: Message Title Timo Sand commented on JENKINS-49105 Re: Can't send data to influx Aleksi Simell I've added list of all enabled plugins and a screenshot of the Influxdbb config Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49105) Can't send data to influx
Title: Message Title Timo Sand updated an issue Jenkins / JENKINS-49105 Can't send data to influx Change By: Timo Sand Attachment: Update_Center__Jenkins_.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49105) Can't send data to influx
Title: Message Title Timo Sand updated an issue Jenkins / JENKINS-49105 Can't send data to influx Change By: Timo Sand Attachment: Update_Center__Jenkins_.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49105) Can't send data to influx
Title: Message Title Timo Sand updated an issue Jenkins / JENKINS-49105 Can't send data to influx Change By: Timo Sand Attachment: Update_Center__Jenkins_.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49105) Can't send data to influx
Title: Message Title Timo Sand updated an issue Jenkins / JENKINS-49105 Can't send data to influx Change By: Timo Sand Attachment: Update_Center__Jenkins_.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49105) Can't send data to influx
Title: Message Title Timo Sand updated an issue Jenkins / JENKINS-49105 Can't send data to influx Change By: Timo Sand Attachment: Update_Center__Jenkins_.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49105) Can't send data to influx
Title: Message Title Timo Sand updated an issue Jenkins / JENKINS-49105 Can't send data to influx Change By: Timo Sand Environment: Jenkins 2. 103 107 Plugin version 1. 13.1 14 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49105) Can't send data to influx
Title: Message Title Timo Sand updated an issue Jenkins / JENKINS-49105 Can't send data to influx Change By: Timo Sand Attachment: Configure_System__Jenkins_.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49105) Can't send data to influx
Title: Message Title Timo Sand commented on JENKINS-49105 Re: Can't send data to influx Aleksi Simell Any progress with this? Is there anything we can do to help? It would be really useful to get stats sent to grafana from Jenkins and without this we're unable to do that Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
