Jenkins organization project won't build a branch that was orphaned / removed after the branch has been restored

2018-01-19 Thread Troy Martin
We have a Jenkins organization project that tracks our company's private 
repositories. Each git branch has a Jenkinsfile at the root of the repo. One of 
the branches, development, was accidentally deleted and then put back. Jenkins 
saw the delete as an orphaned branch and removed it:

Evaluating orphaned items in OrganizationName » repository-name
Will remove development
...
Finished: SUCCESS
Jenkins will no longer build the branch even though it receives the webhook 
event when the branch is updated. It's ignoring it. I ran an organization scan 
and it says

Checking branch development
but takes no action on it. There's no

‘Jenkinsfile’ not found Does not meet criteria

associated with it or any other feedback in the log. It just says 'checking' 
and moves on. I verified the Jenkinsfile exists.

Any idea how I can get Jenkins to start building the branch


Thanks!

Troy
-- 


*This email and any files transmitted with it are confidential and intended 
solely for the use of the individual or entity to whom they are addressed. 
This message contains confidential information and is intended only for the 
individual named. If you are not the named addressee you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this e-mail by mistake and 
delete this e-mail from your system. If you are not the intended recipient 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited*.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/BE1F8E34-9FE2-4C95-8C65-A0CB55B72612%40evosus.com.
For more options, visit https://groups.google.com/d/optout.


Re: Blue Ocean not loading

2018-01-19 Thread Daniel Beck

> On 19. Jan 2018, at 20:42, John  wrote:
> 
> I am running on a locked down system with Firefox 10

It should come as no surprise that a six year old browser is no longer 
supported by a component entirely based on modern web technology.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/390AAAEC-0A8A-43FE-AF3D-FA99E3E35232%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Re: Kills me that BUILD_ID=dontKillMe

2018-01-19 Thread Ioannis Moutsatsos
Simon your suspicion was correct! Thank you!

After downgrading several plugins, I was able to isolate the issue with the 
EnvInject 
Plugin  v2.1.5
This version of the plugin seems to inject 'dontKillMe' as the BUILD_ID for 
a build. This behavior is not present in EnvInject Plugin v2.13
So, I have now settled to v2.1.3 as the latest version of the plugin to 
install.

Best regards
Ioannis

On Wednesday, January 17, 2018 at 2:07:58 PM UTC-5, Simon Richter wrote:
>
> Hi, 
>
> Am 17.01.2018 um 17:25 schrieb Ioannis Moutsatsos: 
>
> > The BUILD_ID (which up to this point was equal to BUILD_NUMBER) is now 
> > set to 'dontKillMe' 
>
> I dimly remember that this is a way to tell the cleanup code that kills 
> all processes after the build has finished to ignore certain processes. 
>
> On Windows with Visual Studio, this is often needed because pdbserv.exe 
> is shared between builds, so if the build that initially started it 
> finishes, all the other builds that are still running will fail. 
>
> Not sure why this is set now, but I'd suspect a plugin rather than 
> Jenkins core here. 
>
>Simon 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c378e0d5-9d7c-4bf7-938f-ac1a9ecf7f74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Blue Ocean not loading

2018-01-19 Thread John
I opened up the error console and there are a lot of css errors, declaration 
dropped. Such as: error parsing background image, display, flex wrap, align 
items. I am running on a locked down system with Firefox 10. I am wondering if 
that's the problem.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/0da4bb8f-3e51-49f9-96f6-78461c10e456%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Blue Ocean not loading

2018-01-19 Thread Victor Martinez
Quick one, did you open the devtools of your browser and saw any javascript 
errors or whatsoever?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/22583df2-e143-4f62-a377-24f41b6a6c5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Blue Ocean not loading

2018-01-19 Thread John
My current work environment is Centos with no network connection. I had to 
install Jenkins on a separate Windows machine to pull all the plugins and 
dependencies. Blue Ocean starts up fine in Windows so I copied the entire 
plugins folder into the Linux system. 

Jenkins installs everything with no errors but Blue Ocean won't load. Clicking 
on the link just takes me to a white page with a blue progress bar above. It 
stops at around 90%. I don't see any errors in the "All Jenkins Logs". What 
other logs or resource can I look at to troubleshoot this?

Jenkins 2.89.2
Blue Ocean 1.4.0

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1a886ee8-d937-45df-9398-74529b5d235f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Jenkins Pipeling ECS deployments plugin

2018-01-19 Thread Kai


Hi,


It would be great if a plugin is available to support new ECS deployments 
where we just specify the ECS cluster, service name and docker image tag, 
and it just takes the existing task definition the service is mapped to and 
updates the image tag to the new one and updates the ecs service to the new 
ecs task revision. Is there a ECS deployment plugin in the works for 
Jenkins pipeline?


Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a504fd83-fb63-4a7a-974a-334627024328%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Disabling Jenkins' new version message

2018-01-19 Thread speak2muhammed
Go to *Manage Jenkins> Configure System> **Administrative monitors 
configuration *and uncheck *Jenkins Update* Notification box
and save the settings and refresh jenkins page. Now you should not see the 
jenkins new version update notification.

On Sunday, May 7, 2017 at 6:20:14 PM UTC-4, Daniel Beck wrote:
>
>
> > On 04.05.2017, at 14:42, Sébastien Hinderer  > wrote: 
> > 
> > Very interesting, thanks! May I ask in which version of Jenkins this 
> > feature has been introduced? 
>
> 2.24. 
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3bfd3797-5e44-4ac3-95f7-642d39c25982%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: secret token sent from gitlab webhook not being checked

2018-01-19 Thread chris . every
I raised https://github.com/jenkinsci/gitlab-plugin/issues/700

looks like it's a bug in the plugin. I'll close this case down (follow the 
github issue for further updates)

On Friday, 5 January 2018 11:09:56 UTC, chris...@paxport.net wrote:
>
> think I'll raise this on the gitlab-plugin github project, but if anyone 
> here has any suggestions that'd be great. I'll post back here if I get any 
> updates.
>
> On Friday, 5 January 2018 10:47:10 UTC, chris...@paxport.net wrote:
>>
>> I'm trying to get the simple "secret token" auth working with multibranch 
>> declarative pipelines on my gitlab webhooks.
>>
>> The webhooks (all "Push Hook") I've got set up seem to be working fine in 
>> the sense that they fire the correct project; the URLs I've got defined in 
>> the gitlab webhooks are of the format: /project/
>>
>> *It's the "secret token" part that's not being checked, regardless of 
>> what I specify*. Checking the details of webhooks that have fired shows 
>> the "X-Gitlab-Token" header being sent correctly.
>>
>>
>> an example snippet from one of my declarative pipelines:
>>
>> options {
>> gitLabConnection('gitlab')
>> }
>> triggers {
>> gitlab(
>> triggerOnPush: true,
>> triggerOnMergeRequest: false, 
>> triggerOpenMergeRequestOnPush: "never",
>> triggerOnNoteRequest: false,
>> noteRegex: "Jenkins please retry a build",
>> skipWorkInProgressMergeRequest: false,
>> ciSkip: false,
>> setBuildDescription: false,
>> addNoteOnMergeRequest: false,
>> addCiMessage: false,
>> addVoteOnMergeRequest: false,
>> acceptMergeRequestOnSuccess: false,
>> branchFilterType: "NameBasedFilter",
>> includeBranchesSpec: "master",
>> excludeBranchesSpec: "",
>> secretToken: "_redacted_")
>> }
>>
>> Once this pipeline has run for a project, I can see all the config 
>> settings showing correctly in the "View Configuration" page of the 
>> project/branch in Jenkins.
>>
>> So from what I can see, everything looks okay.
>>
>> I added a gitlab-plugin log recorder, and can see entries such as: 
>>
>>
>> *"Jan 04, 2018 11:11:57 PM FINE 
>> com.dabsquared.gitlabjenkins.webhook.build.PushBuildAction  Notify 
>> scmSourceOwner  about changes for "*
>> I'm not really au fait with the Jenkins codebase, but doing some quick 
>> digging (and from log entries), suggests the project is an instance of 
>> SCMSourceOwner, as opposed to an instance of Job. The former results in a 
>> SCMSourceOwnerNotifier 
>> which doesn't seem to use secretToken, whereas the latter results in a 
>> TriggerNotifier which DOES use secretToken.
>>
>> So why are my projects instances of SCMSourceOwner, and to get the 
>> secretToken functionality working, do I need to switch it to a Job, 
>> somehow, or will I have some configuration incorrectly set, somewhere?
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/22fd8575-0d30-4bd5-bab9-58868bd102d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Master runs out of disk space because of Jenkins files and libraries loading

2018-01-19 Thread Mark Waite
On Thu, Jan 18, 2018 at 1:22 AM Shiran  wrote:

> Hi all,
>
> I've noticed that when my pipeline jobs start and load the Jenkins file
> and shared libraries, I end up with many copies of the entire repository
> being checked out on the master. This causes master to run out of disk space
>
>
You'll probably need to add more disk space to your master.

There are changes that may reduce disc use, but even with those changes,
Jenkins uses disc space and will continue to use disc space as you use it
more.

Some of the techniques that can reduce disc use:

   - Use the GitHub branch source plugin (or the Bitbucket branch source
   plugin or the Gitea plugin) in the multi-branch pipeline job definition
   rather than the git plugin.  Those higher level branch source plugins
   obtain the Jenkinsfile without using a full checkout (so long as you don't
   disable lightweight checkout)
   - Maintain a git reference repository on each agent with a reasonably
   current copy of the repositories, then add the path to that reference
   repository to the job definition.  The CloudBees support article about
   reference repositories
   

is
   very helpful.  I gave a 10 minute talk at Jenkins World 2017 "Git in the
   Large "  that may
   help.  I also gave a 10 minute talk at Jenkins World 2016 "Jenkins hints
   for large git repos
   ".
   Those two talks are available on youtube (2017
   , 2016
   ) if needed
   - Honor the refspec on checkout (already done by multi-branch pipeline,
   not done by default for freestyle projects or matrix projects)
   - Keep your pipeline library git repositories small and focused on only
   providing pipeline libraries.  Don't include content in a pipeline library
   that is not needed for the pipeline library
   - Create a new git repository which uses "git lfs" instead of storing
   large files directly in the repository

Thanks,
 Mark Waite


>
> *More details:*
>
>
>1. I use Git plugin to load the Jenkins file
>2. Loading shared libraries (stored under "vars" folder) starts at the
>beginning of the build, using this pipeline step:
>library identifier: 'utils', retriever: modernSCM([$class:
>'GitSCMSource', credentialsId: '<   >', id: '<   >', remote: '<   >',
>traits: [[$class: 'jenkins.plugins.git.traits.BranchDiscoveryTrait'], [
>$class: 'RefSpecsSCMSourceTrait', templates: [[value: "  "])
>
>
> *For example:*
>
> I have a job called "*post_job*" and my Jenkins files and libraries are
> stored in a repository called "my_repository".
>
>
> *After loading my Jenkins file:*
>
> /jenkins_home/jenkins/workspace/ post_job@script
>
> è contains all of my_repository content
>
>
> *After loading my lobraries (I have 3: jobFlow, ManifestMap, utils):*
>
>
> /jenkins_home/jenkins/workspace/post_job@libs
>
> jobFlow  è contains all of
> my_repository content
>
> jobFlow@tmpè
> empty
>
> manifestMap è contains all of
> my_repository content
>
>
> manifestMap@tmp   è
> empty
>
>
> utils   è contains all of
> my_repository content
>
>
> utils@tmp è empty
>
>
>
>
> So I have my_repository content 4 times (!!) for each job that I have!
> Any suggestions? please!
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/3f81e9ca-9e1c-437d-87f1-b3e3faeefe86%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGd%3DJO0TCqrhTVQcYcarbJW9zC-2jW%2BvoFYh4nWGCXvRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Search new JDK version with a jenkins job

2018-01-19 Thread Victor Martinez
Hey,

Jenkins itself does use a generated json file which contains the whole list 
of JDK versions:
- http://mirrors.jenkins-ci.org/updates/updates/hudson.tools.JDKInstaller.json

and it's generated with the below crawler script: 
- https://github.com/jenkins-infra/crawler/blob/master/jdk.groovy 

Likely you can extend it 

Cheers


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1835660e-4fa8-43e0-98d7-5563369e67b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.