[JIRA] (JENKINS-56057) UpdateSiteWarningsConfiguration should be confirgurable via JCasC
Title: Message Title Simon Wydooghe commented on JENKINS-56057 Re: UpdateSiteWarningsConfiguration should be confirgurable via JCasC It would be great to be able to suppress certain warnings via JSasC. 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.197480.1549643829000.5553.1567513020360%40Atlassian.JIRA.
[JIRA] (JENKINS-54702) Discover Bitbucket repo when receiving first webhook event
Title: Message Title
Simon Wydooghe created an issue
Jenkins / JENKINS-54702
Discover Bitbucket repo when receiving first webhook event
Issue Type:
Improvement
Assignee:
Unassigned
Components:
bitbucket-branch-source-plugin
Created:
2018-11-19 15:38
Priority:
Minor
Reporter:
Simon Wydooghe
I'm trying to get to a setup where I don't have to scan in Jenkins to discover repo's every time I create a new repository. With GitHub, this is solved by having a Team webhook instead of a webhook per repo. With Bitbucket, the repo's are managed using Terraform, so I can precreate the Jenkins webhook like this:
resource "bitbucket_repository" "example_repo" {
owner = "myteam"
name= "example"
slug= "example"
has_issues = false
has_wiki= false
}
resource "bitbucket_hook" "jenkins" {
owner = "${bitbucket_repository.example_repo.owner}"
repository = "${bitbucket_repository.example_repo.slug}"
url = "" class="code-quote" style="color: #009100">"https://jenkins.example.com/bitbucket-scmsource-hook/notify"
description = "Jenkins hook"
events = [
"repo:push",
"pullrequest:created",
"pullrequest:updated",
"pullrequest:fulfilled",
"pullrequest:rejected",
]
}
Doing this, I assumed that a previously unknown repo would start building when Jenkins receives the first webhook, however this does not seem to be the case. It would be nice if Jenkins would 'discover' the new repository when receiving the first webhook event associated with that new repo.
[JIRA] (JENKINS-34019) ANSIColor plugin leaks format onto next line's timestamp
Title: Message Title Simon Wydooghe commented on JENKINS-34019 Re: ANSIColor plugin leaks format onto next line's timestamp Would be nice to see this fixed if possible... 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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Simon Wydooghe commented on JENKINS-50525 Re: Error When Provisioning Slave: mountPath: Required value Cool, cheers! 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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title
Simon Wydooghe commented on JENKINS-50525
Re: Error When Provisioning Slave: mountPath: Required value
WARNING: Error in provisioning; agent=KubernetesSlave name: jenkins-agent-github-drupal8-site-cms-nieuws-master-59-5b-cdvjx, template=PodTemplate{, name='jenkins-agent-github-drupal8-site-cms-nieuws-master-59-5bjkm', namespace='ops-prod', label='8a6f6637-d8e3-48e6-9c18-8a1f7082675d', serviceAccount='jenkins', nodeSelector='cloud.google.com/gke-preemptible=true,cloud.google.com/gke-local-ssd=true', nodeUsageMode=EXCLUSIVE, volumes=[org.csanchez.jenkins.plugins.kubernetes.volumes.HostPathVolume@63b25977], containers=[ContainerTemplate{name='jnlp', image='medialaan/jenkins-jnlp-slave:3.16-1', alwaysPullImage=true, workingDir='/home/jenkins', args='${computer.jnlpmac} ${computer.name}'}, ContainerTemplate{name='composer', image='medialaan/composer:1.0.0', alwaysPullImage=true, workingDir='/home/jenkins', command='cat', ttyEnabled=true}, ContainerTemplate{name='bazel', image='eu.gcr.io/medialaan-production/bazel:0.1.0', alwaysPullImage=true, workingDir='/home/jenkins', command='cat', ttyEnabled=true}, ContainerTemplate{name='gcp', image='eu.gcr.io/medialaan-production/gcp:0.1.0', alwaysPullImage=true, workingDir='/home/jenkins', command='cat', ttyEnabled=true, envVars=[KeyValueEnvVar [getValue()=$PWD/.kube/config, getKey()=KUBECONFIG], KeyValueEnvVar [getValue()=$PWD/.config, getKey()=CLOUDSDK_CONFIG], KeyValueEnvVar [getValue()=$PWD/.helm, getKey()=HELM_HOME]]}]}
io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://kubernetes.default/api/v1/namespaces/ops-prod/pods. Message: Pod "jenkins-agent-github-drupal8-site-cms-nieuws-master-59-5b-cdvjx" is invalid: [spec.containers[0].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique, spec.containers[1].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique, spec.containers[2].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique, spec.containers[3].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique]. Received status: Status(apiVersion=v1, code=422, details=StatusDetails(causes=[StatusCause(field=spec.containers[0].volumeMounts[1].mountPath, message=Invalid value: "/home/jenkins": must be unique, reason=FieldValueInvalid, additionalProperties={}), StatusCause(field=spec.containers[1].volumeMounts[1].mountPath, message=Invalid value: "/home/jenkins": must be unique, reason=FieldValueInvalid, additionalProperties={}), StatusCause(field=spec.containers[2].volumeMounts[1].mountPath, message=Invalid value: "/home/jenkins": must be unique, reason=FieldValueInvalid, additionalProperties={}), StatusCause(field=spec.containers[3].volumeMounts[1].mountPath, message=Invalid value: "/home/jenkins": must be unique, reason=FieldValueInvalid, additionalProperties={})], group=null, kind=Pod, name=jenkins-agent-github-drupal8-site-cms-nieuws-master-59-5b-cdvjx, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=Pod "jenkins-agent-github-drupal8-site-cms-nieuws-master-59-5b-cdvjx" is invalid: [spec.containers[0].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique, spec.containers[1].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique, spec.containers[2].volumeMounts[1].mountPath: Invalid value: "/home/jenkins": must be unique, spec.containers[3].volumeMounts[1].mountPath: Invalid value: "/home/jenkins":
[JIRA] (JENKINS-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Simon Wydooghe commented on JENKINS-50525 Re: Error When Provisioning Slave: mountPath: Required value I also had to roll back to 1.14 because of issues spinning up pods. The error was also related to the volumes being mounted (a local hostPath volume). It was complaining about the value not being unique or something. I will upgrade it again when Jenkins is not in use to try to reproduce it to provide logs and podTemplate. 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-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title Simon Wydooghe commented on JENKINS-47286 Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view I think people with scripted pipelines could benefit greatly from this. Scripted pipeline users run more advanced pipelines I'm guessing, so it feels weird to not support this feature there as it seems they will be the first ones to implement this functionality in their pipelines. 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-46068) Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)
Title: Message Title Simon Wydooghe edited a comment on JENKINS-46068 Re: Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) I can confirm this behaviour after renaming a bunch of our repositories. What's the easiest workaround to remove the old repo in Jenkins for now? 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-46068) Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected)
Title: Message Title Simon Wydooghe commented on JENKINS-46068 Re: Do not detect renamed GitHub repos under the old name (bonus points if job can be renamed when rename detected) I can confirm this behaviour after renaming a bunch of our repositories. 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.
