My Grails jobs fails on Jenkins provided by Cloudbees because they require to accept UAA agreement.
Is there a way to accept agreements?
Jenkins Grails plugin can be configured to run in non-interactive mode, that should fix this issue
Related
I am an architect completely new to DevOPS and CICD and my question may be not clear. My application vendor has provided some Ansible roles and playbooks. I have Jenkins server which is having a pipeline running a terraform scripts to provision the compute engines on GCP. After this provisioning I will have deploy my application provided by my vendor.
I have couple of questions here
Do you need separate server hosting ansible other than the Jenkins to execute the Ansible roles and playbook? Or Just a Ansible plug-in installed will suffice to execute these ansible roles
For application deployment on the target server provisioned by terraform , We need to tell fill those details dynamically to the hosts files of ansible? Have anyone tried this before or is there any other way.
My target servers where the application will be deployed will have both Windows and Linux. What integrations are required at jenkins level for application deployment pipeline to work?
Thanks,
Manoj
I just concluded my GitHub integration with Jenkins so that every time I commit code to my GitHub repository, Jenkins automatically builds.
Now I'm trying to integrate SonarCloud too but I haven't been successful.
I'm not looking to integrate with a local SonarQube server, I really need SonarCloud for my team to check it every time Jenkins builds.
I'm not sure if I should analyse the project locally to achieve this or if I can analyse my Jenkins server or GitHub repository and get the result I want because I can't find any documentation.
Can anyone point me in the right direction?
Thank you!
Sonarcloud is just a sonarqube server.
Just use sonar-scanner(the documentation for jenkins can be found here).
At first, you need to install the jenkins plugin for sonar-scanner.
After that, you open the configuration of sonar-scanner using Manage Jenkins > Configure System.
Insert https://sonarcloud.io under Server URL and your sonar token(of sonarclound) under Server authentication token
Under Manage Jenkins > Configure System, you should check Enable injection of SonarQube server configuration as build environment variables and in Build Environment in your job, you should enable Prepare SonarScanner environment.
After you've done that, you can run sonar-scanner with $SONAR_MAVEN_GOAL (if you are using maven), ./gradlew sonarqube (if you are using gradle) or sonar-scanner (if you use none of that).
I am getting error while integrating jenkins with JIRA.
Both JIRA and jenkins are hosted on same server.
Provided application URL in JIRA is my-ip:8080
error: No response was received from the URL you entered - it may not be valid. Please fix the URL below, if needed, and click Continue.
What ports are JIRA & Jenkins running on? Usually JIRA and Jenkins like to run on the same port (8080) by default. You can change the default port for starting Jenkins as ala something like java -jar jenkins.war --httpPort=9090
Did you see this link: Configuring the Atlassian JIRA plugin to work with Jenkins CI system
We are using Hudson as a CI tool. At present we are needed to use Jenkins, to deploy the build to Stage, Prod environment. What is the best aproach we should follow.
I know about promote buld plugin, but the issue is authentication. I want whevener we need to promote a build to deploy to Stage or Prod, it should ask for netqwork credential first. And then the promote job should execute the Batch command using the creadential supplied. At present, the promote plugin, runs using the credentials which the Tomcat server is configured to run.
Same issue with Build Pipeline plugin.
I want only dev or even hudson admin also should not be able to execute the promote build unless credential supplied. (We have windows 2008 r2 OS)
Can you please help me in resolving the issue. so that basically whenever a user click on Promote build to QA\Stage\Prod the plugin should ask for credential or should use the logged on users credential and execute the batch script using the logged users credential only and not by using the credentials of the account with which the tomcat server is configured.
Can you please help me?
Please suggests us the best aproach for making automated build on prod\stage.
For deployment I normally use SSH, Private/Public keys takes care of the authentication problems normally associated with running commands on other servers.
SSH is normally associated with unix based systems, but it does support windows.
Finally, I would recommend considering decoupling your build system (jenkins) from the system performing the deployment by using an intermediate repository. See the following answer for more details:
Jenkins : how to check out artifact from Nexus and Deploy on Tomcat-
I've just migrated my CI server from an In company server to a CloudBees server.
My application uses JBehave for functional testing and on the In Company server, i had JBehave hudson plugin (http://jbehave.org/reference/stable/hudson-plugin.html) configured. In this setup my tests was always failling sillently, so after the build process, The plugin would parse the jbehave results files and mark which tests had failled, with detailled information.
Now, on cloudbees it seems that I can't install this plugin. So, what should I do? Stop failling sillently? If I do so, the feedback from tests is very Coarse grained, and they would not be helpful for developers to discover exactly which step had failled.
Is there a way to use JBehave Hudson Plugin inside cloudbees Environment?
Thanks in Advance, and sorry for my bad english.
You can get this jenkins/hudson plugin installed on DEV#Cloud as long as you have a for-pay subscription. In such case, log in to GrandCentral and use the support link to request plugin installation on your instance.
FREE accounts are restricted to the "essential list"
Update :
CloudBees announced that all subscriptions now will have all (compatible) community plugins available.