Re: Store (small) table data in Jenkins without external database

You could create a job with an HTML description that’s your data table... On Tue, Nov 13, 2018 at 23:17 Nick Mellor wrote: > Hi, > > I'm building a Jenkins front-end for a small team of developers. I need to > store name, email, permission level and one or two other bits of data per >

Store (small) table data in Jenkins without external database

Hi, I'm building a Jenkins front-end for a small team of developers. I need to store name, email, permission level and one or two other bits of data per developer. Passwords can be handled by the credentials facility. My employer is not AT ALL happy about spending money, so doesn't want even

Re: calling another job from parent job

As far as I'm aware off, the run of each 'job/pipeline' is independent therefore all the stages, in any downstream* job, won't be shown in the upstream job unfortunately. The only way I'm aware of, is using a shared library/pipeline to call the same steps that the downstream job runs. *** aka

Pipeline: Publish RPM to Nexus Repository Manager

Publish RPM artifacts to Sonatype Nexus yum repository. It seems the nexus artifact uploader plugin is used for uploading non-maven artifacts to Nexus Repository Manager. It says this plugin is used to upload non-maven artifacts to Nexus, but it requires a few properties that are quite not

Jenkins, Docker agents, and /etc/environment

I have some proxy settings defined in the /etc/environment files of my Docker images which constitute my Jenkins agents. These images are correctly spun up and Jenkins happily builds within them, with one issue: the variables from /etc/environment aren't present in the agent environment. When

Re: custom image for jnlp( amazonlinux)

Here is the error logs while using custom image Error in provisioning; agent=KubernetesSlave name: eks-cluster-qwx9k, template=PodTemplate{inheritFrom='', name='eks-cluster', namespace='', slaveConnectTimeout=30, label='eks-cluster', nodeSelector='', nodeUsageMode=NORMAL,

Re: calling another job from parent job

Are you using a Jenkinsfile or are you doing this in the Jenkins job config page? On Tuesday, November 13, 2018 at 12:56:57 AM UTC-5, Akshay Paturkar wrote: > > Hi All, > i am trying to call job from another job and able to do it by following > below instructions . >

Re: How to handle complex job dependency?

I ended up following Martin's advice and tagged my docker images in AWS ECR accordingly by following the steps outlined Retagging an Image with the AWS CLI . So when I deploy 1.0.0 to sandbox successfully, the

Why are Folder Properties key/value pairs not recognized in multi-branch pipeline job?

I installed the Folder Properties plug in, and define these GIT_BRANC = feature/dev-1234-some-work RUN_TESTS = true DEPLOY_TO_SANDBOX = true I then have this in my Jenkinsfile def echoStr = """ Git branch:

Re: How to handle complex job dependency?

thanks, this doesn't help me. On Tuesday, November 13, 2018 at 12:56:54 AM UTC-5, Matt Hicks wrote: > > It doesn't have pipeline support, but the promoted builds plugin > can do > this for freestyle jobs. > -- You received this

Re: SSLError

take a look at this issue of the Azure CLI https://github.com/Azure/azure-cli/issues/5099 I think is your issue. El lunes, 12 de noviembre de 2018, 19:02:44 (UTC+1), gotvi...@gmail.com escribió: > > Need urgent help. Trying to run a job in Windows Slave and getting this > error. Please help.

Re: Issue with spaces in string parameter

Am Dienstag, 13. November 2018 00:23:02 UTC+1 schrieb Martin d'Anjou: > > I doubt that would fix it, I was curious and try it. Jenkins trims, but it > does not split the value on spaces. > > The problem might be on how you pass the value to your python script. Can > you share that? > > Just to