Windows Service Wrapper - YAML configurations support project announce

[Buddhika Chathuranga]

Hi all,

I'd like to announce the project "Windows Service Wrapper : YAML 
configuration support" which is selected as a Google summer of code project 
in this summer. I am final year student of University of Moratuwa, Sri 
Lanka and I am working with Jenkins on this project this summer.

*Abstract*

On Windows machines, Jenkins master and agents can be installed as Windows 
Services in order to get better robustness and manageability within the 
system. This is a functionality bundled into the Jenkins core directly. 
When installed as a service, Jenkins uses the Windows Service Wrapper 
executable (.NET, written in C#) which is being configured by XML config 
files. Currently, there are only a few configuration checks there (no XML 
Schema, limited validation, etc.), and it’s often that the service wrapper 
is misconfigured by Jenkins users.

In this project we propose to update Windows Service Wrapper to support 
YAML files as configuration inputs and to introduce better configuration 
validation during the service installation and startup. Usage of YAML 
should simplify configuration management in Jenkins, especially when 
automated tools are used.

*Team*

Student: Buddhika Chathuranga
Mentor : Oleg Nenashev
Mentor : Michael Cirioli
Mentor : Next Turn

*Project page*
https://www.jenkins.io/projects/gsoc/2020/projects/winsw-yaml-configs/

*Office Hours*
Office hours are scheduled every Tuesday at 13:30 UTC in the project’s 
Gitter chat.

*Meeting Notes*
https://docs.google.com/document/d/1eq1M1buaEMmRQ3XLFRFnTbJpRnHu1fnqxmTHPKm8WjU/edit?usp=sharing

*Chat*
We are using gitter chat - https://gitter.im/winsw/winsw

Best Regards,
Buddhika Chathuranga.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/43d52060-e7a2-4afc-a6cb-f1c8d2a8d0c8%40googlegroups.com.

Re: Unable to perform plugin release to repo.jenkins-ci.org

[Slide]

Great, glad things are working for you. I haven't used the method with
Artifactory, so I didn't know if it worked or not :)

On Tue, May 26, 2020 at 7:32 AM Tyler Camp 
wrote:

> Mez and slide, the password provided by artifactory did end up working. I
> tried the encryption method that you mentioned, slide, and got a password
> significantly different from artifactory that did not work.
>
> Thank you for your suggestion Daniel, after making that change (leftover
> from very old pom) and restarting the release process I was able to deploy
> our release using the encrypted artifactory password.
>
> On Saturday, May 23, 2020 at 3:27:39 AM UTC-4, Daniel Beck wrote:
>>
>> If your plugin overrides the distributionManagement, as in
>>
>>
>> https://github.com/jenkinsci/codedx-plugin/blob/d56180188ae138677f09214f57c1b8d840375477/pom.xml#L70-L75
>>
>> our instructions no longer apply.
>>
>> In this case, it is named 'repo.jenkins-ci.org', not the default '
>> maven.jenkins-ci.org', so the credentials need to be changed to apply to
>> the same server ID.
>>
>> Although the real fix is to rip out this nonsense from the pom.xml.
>>
>>
>> > On 22. May 2020, at 19:21, Tyler Camp  wrote:
>> >
>> >
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/7eae5673-f8eb-4bb5-b5f4-442b0dc4b7d6%40googlegroups.com
> 
> .
>


-- 
Website: http://earl-of-code.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVd1N5O-iZ9VLFNq-GPBPpjn3MPioxiDDEhzOd%2Bi65VzBA%40mail.gmail.com.

Re: Unable to perform plugin release to repo.jenkins-ci.org

[Tyler Camp]

Mez and slide, the password provided by artifactory did end up working. I 
tried the encryption method that you mentioned, slide, and got a password 
significantly different from artifactory that did not work.

Thank you for your suggestion Daniel, after making that change (leftover 
from very old pom) and restarting the release process I was able to deploy 
our release using the encrypted artifactory password.

On Saturday, May 23, 2020 at 3:27:39 AM UTC-4, Daniel Beck wrote:
>
> If your plugin overrides the distributionManagement, as in 
>
>
> https://github.com/jenkinsci/codedx-plugin/blob/d56180188ae138677f09214f57c1b8d840375477/pom.xml#L70-L75
>  
>
> our instructions no longer apply. 
>
> In this case, it is named 'repo.jenkins-ci.org', not the default '
> maven.jenkins-ci.org', so the credentials need to be changed to apply to 
> the same server ID. 
>
> Although the real fix is to rip out this nonsense from the pom.xml. 
>
>
> > On 22. May 2020, at 19:21, Tyler Camp  > wrote: 
> > 
> > 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7eae5673-f8eb-4bb5-b5f4-442b0dc4b7d6%40googlegroups.com.

Re: Configuration Slicing plugin adoption

[Guy Sheffer]

Note.
I can also see the release in Artifactory:
https://repo.jenkins-ci.org/webapp/#/artifacts/browse/tree/General/releases/org/jenkins-ci/plugins/configurationslicing/1.50

Also its not available on Jenkins plugin manager.

And to recap, can't see it in: 
https://plugins.jenkins.io/configurationslicing/




On Monday, May 25, 2020 at 5:23:36 PM UTC+3, Guy Sheffer wrote:
>
> Thanks, the url that tim gave me the right settings to put in to 
> ~/.m2/settings.xml
> (Also figuring out that you need to click on your username and NOT on the 
> word "welcome" to reach the profile in artifactory was a little hidden)
>
> I have made the release on Github, and it seems to appear there.
> However the Jenkins page seems to still have the old version of the plugin.
> How do I update this?: https://plugins.jenkins.io/configurationslicing/
>
> For comparison, new version is here: 
> https://github.com/jenkinsci/configurationslicing-plugin/releases
>
> On Monday, May 25, 2020 at 10:47:48 AM UTC+3, Tim Jacomb wrote:
>>
>> Also:
>>
>> https://www.jenkins.io/doc/developer/publishing/releasing/
>>
>> On Mon, 25 May 2020 at 08:32, Oleg Nenashev  wrote:
>>
>>>
>>> https://wiki.jenkins.io/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkins-ci.org
>>>   
>>> provides Maven settings.xml configuration guidelines 
>>>
>>> On Mon, May 25, 2020 at 9:26 AM Guy Sheffer  wrote:
>>>
 Thanks guys, hopefully this would let me fully adopt and maintain the 
 plugin, joining you.

 Seems like its approved but I still get an unauthorised message. Do I 
 need to put my artifactory permissions somewhere so mvn picks them up?
 Command for reference:
 mvn release:prepare release:perform



 On Sunday, May 24, 2020 at 10:46:53 PM UTC+3, Oleg Nenashev wrote:
>
> I will review it once I get to the computer. 
>
> BR, Oleg
>
> On Sun, May 24, 2020, 21:45 'Gavin Mogan' via Jenkins Developers <
> jenkin...@googlegroups.com> wrote:
>
>> There's only a couple people that can approve, and its a volunteer 
>> organization, its especially slow on weekends because people have 
>> family. 
>> It'll get done
>>
>> Gavin
>>
>> On Sun, May 24, 2020 at 12:42 PM Guy Sheffer  
>> wrote:
>>
>>> Ok, waiting for someone with permissions to approve this:
>>>
>>> https://github.com/jenkins-infra/repository-permissions-updater/pull/1536
>>>
>>> On Friday, May 22, 2020 at 8:30:24 PM UTC+3, Richard Bywater wrote:

 Your current pom.xml file has a non-SNAPSHOT version in it. When 
 doing a release the process expects (as far as I know) to find a 
 SNAPSHOT 
 version there, and the process then changes that to a non-SNAPSHOT, 
 releases, and then ups the version number to the next SNAPSHOT number.

 Richard.

 On Fri, 22 May 2020 at 12:18, Guy Sheffer  wrote:

> Ran that and got this:
>
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  25.037 s
> [INFO] Finished at: 2020-05-22T03:17:54+03:00
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare 
> (default-cli) 
> on project configurationslicing: You don't have a SNAPSHOT project in 
> the 
> reactor projects list. -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven 
> with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug 
> logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible 
> solutions, please read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
>
>
> Am I doing something wrong?
>
> On Friday, May 22, 2020 at 2:56:19 AM UTC+3, Gavin Mogan wrote:
>>
>> a standard `mvn release:prepare release:perform` will do all the 
>> tagging and releasing for you
>>
>> On Thu, May 21, 2020 at 4:54 PM Guy Sheffer  
>> wrote:
>>
>>> Ok, looks like it finally builds successfully in the CI. Should 
>>> I tag it and release? Or do we need to do more testing first?
>>>
>>> On Tuesday, May 19, 2020 at 1:11:51 PM UTC+3, Oleg Nenashev 
>>> wrote:

 So you get static analysis errors from SpotBugs.
 It is important to review and clean up them eventually, but for 
 the time 

Jenkins Kubernetes only executes "built in" jenkins/jnlp-slave:4.0.1-1?

[Jon Brohauge]

Hi all,

I'm stuck trying to work on a master/agent setup, running on kubernetes.

I've watched the demonstration video (
https://www.youtube.com/watch?v=h4hKSXjCqyI) by Marky Jacksonm which helped 
me a ton.

My issue is that when I try to run my test-job (the attached Jenkinsfile), 
it only seems to execute on the built in 
container: jenkins/jnlp-slave:4.0.1-1. I don't see that execution is handed 
over to my custom agent (the attached Dockerfile).

I've attached the Jenkinsfile for the test-job, a redacted/amputated 
Dockerfile of my custom jenkins-agent, an example of the output of the 
test-job (job-output.txt), output taken from running the 
jenkins/jnlp-slave:4.0.1-1 image directly (jnlp-slave-4.0.1-1.info.txt), 
and my Kubernetes cloud configuration (Kubernetes-cloud-configuration.txt).

Due to corporate non-disclosure, I've had to remove some parts, but I've 
replaced the relevant parts with "[...]" meaningful placeholders.

Regards,
Jon

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ac3ba8f6-9a1d-46ef-ac46-67de125821ab%40googlegroups.com.
[Pipeline] Start of Pipeline
[Pipeline] node
Still waiting to schedule task
‘Jenkins’ doesn’t have label ‘inbound-agent’
Agent inbound-agent-73tq7 is provisioned from template inbound-agent
---
apiVersion: "v1"
kind: "Pod"
metadata:
  labels:
jenkins: "slave"
jenkins/label: "inbound-agent"
  name: "inbound-agent-73tq7"
spec:
  containers:
  - args:
- "cat"
command:
- "/bin/sh"
- "-c"
image: "[CUSTOM JENKINS AGENT]"
imagePullPolicy: "Always"
name: "k8s-container-template-01"
resources:
  limits: {}
  requests: {}
securityContext:
  privileged: false
tty: true
volumeMounts:
- mountPath: "/home/jenkins"
  name: "workspace-volume"
  readOnly: false
workingDir: "/home/jenkins"
  - env:
- name: "JENKINS_SECRET"
  value: ""
- name: "JENKINS_AGENT_NAME"
  value: "inbound-agent-73tq7"
- name: "JENKINS_NAME"
  value: "inbound-agent-73tq7"
- name: "JENKINS_AGENT_WORKDIR"
  value: "/home/jenkins/agent"
- name: "JENKINS_URL"
  value: "http://10.244.2.6:8080/;
image: "jenkins/jnlp-slave:4.0.1-1"
name: "jnlp"
resources:
  requests:
cpu: "100m"
memory: "256Mi"
volumeMounts:
- mountPath: "/home/jenkins/agent"
  name: "workspace-volume"
  readOnly: false
  hostNetwork: false
  nodeSelector:
beta.kubernetes.io/os: "linux"
  restartPolicy: "Never"
  securityContext: {}
  serviceAccount: "jenkins"
  volumes:
  - emptyDir:
  medium: ""
name: "workspace-volume"

Running on inbound-agent-73tq7 in 
/home/jenkins/agent/workspace/ci-test_tool-versions_kubernetes
[Pipeline] {
[Pipeline] ansiColor
[Pipeline] {
[Pipeline] stage
[Pipeline] { (info)
[Pipeline] sh
+ pwd
/home/jenkins/agent/workspace/ci-test_tool-versions_kubernetes
[Pipeline] sh
+ ls -la
total 8
drwxr-xr-x 2 jenkins jenkins 4096 May 26 04:48 .
drwxr-xr-x 4 jenkins jenkins 4096 May 26 04:48 ..
[Pipeline] sh
+ whoami
jenkins
[Pipeline] sh
+ echo inbound-agent-73tq7
inbound-agent-73tq7
[Pipeline] sh
+ export
export AGENT_WORKDIR='/home/jenkins/agent'
export BRANCH_NAME='kubernetes'
export BUILD_DISPLAY_NAME='#6'
export BUILD_ID='6'
export BUILD_NUMBER='6'
export BUILD_TAG='jenkins-jenkins-ci-test-tool-versions-kubernetes-6'
export BUILD_URL='https://[JENKINS 
HOSTNAME]/job/jenkins-ci-test/job/tool-versions/job/kubernetes/6/'
export EXECUTOR_NUMBER='0'
export HOME='/home/jenkins'
export HOSTNAME='inbound-agent-73tq7'
export HUDSON_COOKIE='1f0b762f-da96-4278-9e2e-ba322983e400'
export HUDSON_HOME='/var/jenkins_home'
export HUDSON_SERVER_COOKIE='02ab1f383a78a006'
export HUDSON_URL='https://[JENKINS HOSTNAME]/'
export 
JAVA_BASE_URL='https://github.com/AdoptOpenJDK/openjdk8-upstream-binaries/releases/download/jdk8u242-b08/OpenJDK8U-jdk_'
export JAVA_HOME='/usr/local/openjdk-8'
export JAVA_URL_VERSION='8u242b08'
export JAVA_VERSION='8u242'
export JENKINS_AGENT_NAME='inbound-agent-73tq7'
export JENKINS_AGENT_WORKDIR='/home/jenkins/agent'
export JENKINS_HOME='/var/jenkins_home'
export JENKINS_NAME='inbound-agent-73tq7'
export JENKINS_NODE_COOKIE='29ff8057-4917-47ba-9f2c-8a665744e37f'
export JENKINS_PORT='tcp://10.98.197.70:80'
export JENKINS_PORT_80_TCP='tcp://10.98.197.70:80'
export JENKINS_PORT_80_TCP_ADDR='10.98.197.70'
export JENKINS_PORT_80_TCP_PORT='80'
export JENKINS_PORT_80_TCP_PROTO='tcp'
export JENKINS_SECRET=''
export JENKINS_SERVER_COOKIE='durable-a061d9e7b627258162a5da8a96448dfc'
export JENKINS_SERVICE_HOST='10.98.197.70'
export JENKINS_SERVICE_PORT='80'
export JENKINS_URL='https://[JENKINS HOSTNAME]/'
export JOB_BASE_NAME='kubernetes'
export