date:20200414

[JIRA] (JENKINS-61909) ERROR: The container started but didn't run the expected command.

2020-04-14 Thread he...@tomlankhorst.nl (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Lankhorst created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61909  
 
 
  ERROR: The container started but didn't run the expected command.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 docker-workflow-plugin  
 
 
Created: 
 2020-04-15 06:51  
 
 
Environment: 
 Ubuntu 18.04  Jenkins 2.150  docker-workflow 1.21  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Tom Lankhorst  
 

  
 
 
 
 

 
 When running an image with an entrypoint: > ERROR: The container started but didn't run the expected command. However, when I inspect manually `docker top `, I do see the `cat` command right there. My entrypoint is of the form: #!/bin/bash set -e source "/opt/some/source.bash" exec "$@"      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-61908) Do not mount Jenkins container volumes on Job containers

2020-04-14 Thread he...@tomlankhorst.nl (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tom Lankhorst created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61908  
 
 
  Do not mount Jenkins container volumes on Job containers   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 docker-workflow-plugin  
 
 
Created: 
 2020-04-15 06:40  
 
 
Environment: 
 Ubuntu 18.04  Jenkins 2.150  docker-workflow 1.21  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Tom Lankhorst  
 

  
 
 
 
 

 
 The plugin checks for `containerId.isPresent()`, then tries to mount all volumes mounted on the Jenkins container on the new Job container. This is exactly what I want to prevent since it poses a huge attack surface for untrusted code. https://github.com/jenkinsci/docker-workflow-plugin/blob/1089131014350e11adfa364d34e7717954350261/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java#L168 Suggestion: make this behaviour configurable.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-61778) build job won't trigger if filled in for loop

2020-04-14 Thread nils.ge...@digitalwerk.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nils Gerke commented on  JENKINS-61778  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: build job won't trigger if filled in for loop   
 

  
 
 
 
 

 
 So platform is mutable in the for loop, good to know   
 

  
 
 
 
 

 
 
 

 
 
 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.205617.1585822916000.11353.1586931000276%40Atlassian.JIRA.

[JIRA] (JENKINS-61778) build job won't trigger if filled in for loop

2020-04-14 Thread nils.ge...@digitalwerk.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nils Gerke closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61778  
 
 
  build job won't trigger if filled in for loop   
 

  
 
 
 
 

 
Change By: 
 Nils Gerke  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 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.205617.1585822916000.11354.1586931000306%40Atlassian.JIRA.

[JIRA] (JENKINS-61855) Doxygen parser doesn't detect Doxygen Warnings

2020-04-14 Thread nils.ge...@digitalwerk.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nils Gerke commented on  JENKINS-61855  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Doxygen parser doesn't detect Doxygen Warnings   
 

  
 
 
 
 

 
 Ulli Hafner if you give me a hint were to start, I would try fixing this. I guess the workflow would be to fork https://github.com/jenkinsci/analysis-model, assign this Issue to me and create a pull request when finished right?  
 

  
 
 
 
 

 
 
 

 
 
 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.205718.1586441411000.11351.1586929080061%40Atlassian.JIRA.

[JIRA] (JENKINS-61895) Cannot see all logs after introducing a parallel run

2020-04-14 Thread karthi...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Karthik Palanisamy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61895  
 
 
  Cannot see all logs after introducing a parallel run
 

  
 
 
 
 

 
Change By: 
 Karthik Palanisamy  
 

  
 
 
 
 

 
 Hello, We have recently introduced a parallel run in our Integration stage. The main functionality is to run the postman tests however the parallel was intorduced to deploy two different environments before running the actual tests. Since this change was added, we dont see the newman run logs anymore in Blue Ocean because we only see the two additional steps (where only the deployment logs are there) and the newman run execution is called after this internal parallel is complete. stageIntegration(){-- ---  parallel(       ParallelStep1:  {  {          -blah--           -blah--         }             ParallelStep2:  \  {           -blah--           -blah--         }  )      newman run ..  } So in short, from the above, we see three stages in the blue ocean such as Integration, ParallelStep1, ParallelStep2 but we are missing the logs    for the newman run step.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail

2020-04-14 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-61597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61597  
 
 
  FreeBSD OS version label is wrong in a FreeBSD jail   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 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.205294.1584676136000.11349.1586926320087%40Atlassian.JIRA.

[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail

2020-04-14 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite started work on  JENKINS-61597  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
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.205294.1584676136000.11348.1586926020220%40Atlassian.JIRA.

[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail

2020-04-14 Thread mark.earl.wa...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Mark Waite  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61597  
 
 
  FreeBSD OS version label is wrong in a FreeBSD jail   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 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.205294.1584676136000.11347.1586926020158%40Atlassian.JIRA.

[JIRA] (JENKINS-61868) BuildMaster plugin - Cannot create first build of release for application

2020-04-14 Thread andrew.sum...@outlook.co.nz (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Sumner commented on  JENKINS-61868  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BuildMaster plugin - Cannot create first build of release for application   
 

  
 
 
 
 

 
 I know why that is happening, will fix asap  
 

  
 
 
 
 

 
 
 

 
 
 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.205733.1586533749000.11346.1586922900120%40Atlassian.JIRA.

[JIRA] (JENKINS-61907) Developer can see ANSI color in full log view

2020-04-14 Thread cmurphy...@bloomberg.net (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Charles Murphy updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61907  
 
 
  Developer can see ANSI color in full log view   
 

  
 
 
 
 

 
Change By: 
 Charles Murphy  
 
 
Summary: 
 Developer can see  AMSI  ANSI  color in full log view  
 

  
 
 
 
 

 
 
 

 
 
 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.205779.1586920378000.11344.1586920440307%40Atlassian.JIRA.

[JIRA] (JENKINS-61907) Developer can see AMSI color in full log view

2020-04-14 Thread cmurphy...@bloomberg.net (JIRA)

Title: Message Title

Charles Murphy created an issue

Jenkins / JENKINS-61907

Developer can see AMSI color in full log view

Issue Type:
Story

Assignee:
Unassigned

Components:
blueocean-plugin

Created:
2020-04-15 03:12

Labels:
pipeline-improvement technical-debt

Priority:
Major

Reporter:
Charles Murphy

I understand that the ansiColor plugin and step, as of 0.6.0, when applied, will permit ansi-coloured console data to be correctly displayed for both blue ocean console and classic views. We are very grateful for that. We use blue ocean in our team and I found that to work as described. Now, when viewing a pipeline, whenever there is too much logging to fit in a blue ocean console, it is truncated, and a clickable button to 'show complete logs' appears near the top. When this is clicked, you get a log file displayed in the web browser. It is this log view that I am referring to. A similar log view can be found by clicking the 'pop out' symbol above and to the right of the output section in blue ocean. There is also something known as pipeline.log which can be found when you click on the artifacts tab on blue ocean which is simply the summation of all the output across the pipeline in the same format as the aforementioned logs. All of these log views seem to contain the ansi-color symbols even when the ansiColor plugin and step are in use. After chatting with Jesse Glick regarding the related Jira JENKINS-41200 and the related improvement to the ansiColor plugin https://github.com/jenkinsci/ansicolor-plugin/pull/132, he advised that this was a blue-ocean issue and that it was not part of the scope of the previous work in this area.

1 2 >

1 - 100 of 114 matches

Mail list logo