I've got a trac system v0.12.3 on remote host (mysvn.ru) and I haven't any access to the file trac.ini.
And I have to modify trac workflow from admin panel. May be with the help of some plugins.
I have trac_ini_editor plugin there, but I can't remove current options with it, only add new ones.
What plugins can modify trac workflow from admin panel?
Everything of your workflow changes can be done in trac.ini. Use TracIniAdminPanelPlugin to do that via web interface in case you only have remote access.
install AdvancedTicketWorkflowPlugin. Have advancedworkflow.*
= enabled in your [components] section of trac.ini.
Have workflow = ConfigurableTicketWorkflow,TicketWorkflowOpOwnerReporter in your [ticket] section of trac.ini.
Define your own workflow in a new trac.ini section [ticket-workflow]. The wiki page of AdvancedTicketWorkflowPlugin will explain that in detail.
Related
For every repository there are two "commit mention" settings enabled by default.
Is there a way to disable one of these or both by default (per project or even org) when a new repo is created?
I did not find any project or org setting in the web ui. Can this maybe done using some rest api?
Thank you
Instead of manually changing these options you can use the very same API as the WebUI does:
Endpoint:
https://dev.azure.com/{ORG}/{PROJECT-ID}/_api/_versioncontrol/UpdateRepositoryOption?__v=5&repositoryId={REPO-ID}
Request Type:
POST
Payload:
{"key":"WitResolutionMentionsEnabled","value": <true|false>}
Project ID and REPO ID (hash values) can be extracted either using the Developer Tools in your browser or using the Python API Wrapper.
I searched and tried with the related REST API (Repositories - Update) and Azure CLI (az repos), but did not find any available interface can change two option on repository settings.
Looks like, currently we have no available method to change the options of repository settings in batches. You may need to manually change these options.
If your projects really need this feature, I recommend that you can report a feature request on Developer Community. That will allow you to directly interact with the appropriate product team, and make it more convenient for the product team to collect and categorize your suggestions.
I am setting up a CI/CD system at my company based on Jenkins and SonarQube and I already integrated LDAP in both. I am using Role based plugin in Jenkins and the problem is Jenkins allows me (as Administrator) to assign user to a specific role without requiring that user to login Jenkins in advance. But Sonar with LDAP only create users after logging in, which leads to having to ask at least 8 people (for each project) to go to my Sonar Server page first for authorization. Here's my question: Is there any tools/plugins to match authentication on Jenkins and Sonar, such as people config their own projects on Jenkins can also view bugs/config their projects on Sonar? I appreciate any alternative suggestions. My thanks in advance!
There is no tool or plugin doing this for you. You can assign groups to the user per project and use them in SonarQube to assign the projects.
Or you can create the users manually for SonarQube (Source):
Write directly to the database (there is a simple table called users).
Write a java application that depends on the sonar plugin API, you can then use constructor injection to get a Sonar hibernate session
and persist the user you want. See Here.
How do you setup the remote host field for Jenkins Parameterized Remote Trigger Plugin? The documentation doesn't seem clear to me, and this explanatory blog post has some Jenkins UI features that I can't locate.
This article suggests going to Manage Jenkins > Configure Credentials to add a Domain, but when I go there I see no "Add Domain" button:
The plugin wiki shows screenshots of a section on a page labelled "Parameterized Remote Trigger Configuration". How do I view this section in Jenkins, where is it? I thought it might be in Manage Jenkins > Manage Plugins, but there is no "Manage" or "Configure" button there:
How do I add a "Host" to my Parameterized Remote Trigger Plugin so that I can use it in a Jenkins job?
Update: The official Parameterized Remote Plugin has gone stale and may not fully work. sap-production appears to be maintaining a much more up-to-date version here. You can install it on your instance by cloning the repo then running mvn package. Then install the ./target/Parameterized-Remote-Trigger.hpi file using Manage Jenkins > Manage Plugins > Advanced (tab) > Upload Plugin
It appears that the Jenkins UI has changed over time. Here is how it works now.
Add The Domain
On the left sidebar of the main Jenkins UI, click Credentials > System > Add domain
Name the domain whatever you like, then click Add > Hostname
Fill in the IP or hostname of the remote Jenkins instance in "Includes"
Set Up Credentials
The previous step leaves you on a page with an "Add Credentials" button. Click that. If you can't find it, then you can locate it from the main view via: Credentials > System > Your Domain
If not already selected, then select "Username with password". Choose a scope.
Fill in all the fields as shown. I personally recommend creating a new user on the remote Jenkins and generating an API token and using that here, but you could also just generate an API token for your own user. Click OK.
Configure Parameterized Remote Trigger Plugin
From the main Jenkins page click Manage Jenkins > Configure System, then scroll down to the Parameterized Remote Trigger Configuration section and click Add.
Fill out at least the Authentication and Remote address and port properties, then click Save.
Add Build Step In Job
Open an existing Jenkins job or create a new one, scroll down to the Build section, and add the build step Trigger a remote parameterized job:
Select your host, and fill the rest of the values in.
This is well documented on the plugin's wiki page. See the "System configuration option" section. If you're having trouble with one of the fields specifically, please add more detail to your question.
I have created a workflow which lets Admin publish document.
It's a basic workflow.
What I want is to bypass process for Admin, currently what is happening is that Administrator have to create/approve/publish , Administrator can publish changes directly by not following these steps.
Any help is appreciated.
Thanks.
We have done it by adding this condition.
This is not possible using basic workflow. You can do it either by using advanced workflow (since v7) or by customizing EditMenu.ascx.cs (and underlying classes) + probably CMSDocumentManager. If you want to use workflow just for versioning purposes, use "Automatically publish changes" option on 'General' tab of basic workflow.
I have an organization on GitHub with private repositories. I also have Jenkins set up running on port 8080 on a server, with the GitHub plugin installed. I've created an account on GitHub for my jenkins user, which resides in the owners group.
I'm trying to trigger a job on jenkins when a change is pushed to my development branch (or master branch, neither seem to be working).
When I look at the GitHub Hook Logs in Jenkins, it says that Polling has not run yet. When I go to "Manage Jenkins", the GitHub plugin says my account is Verified when I test it.
Any insight on how to configure this? I have multiple repositories I'd like to work with, so deploy keys don't seem like the solution to me.
Update:
As Craig Ringer mentions in his answer, you can select Grant READ permissions for /github-webhook in "Configure Jenkins" under the GitHub plugin settings, allowing the webhook to be called without authentication.
Another update: Webhooks are now (Dec. 2014) available for organization: see WebHooks API for orgs.
Note: the issue 4 of the hudson-github-plugin was about:
Last GitHub Push
Polling has not run yet.
And the conclusion was:
Nevermind, the only missing piece was a permission checkbox for the github user which ain't documented anywhere on the internet.
So is this a permission issue regarding your Jenkins users?
The article "Set up Jenkins-CI on Ubuntu for painless Rails3 app CI testing" includes the following process:
To restrict the CI system and give access to your Team members to use or see the build logs, first you’ve to create an account.
Go to Manage Jenkins > Configure System,
Check the Enable Security checkbox
Under Security Realm, choose Jenkins's own user database
Check the Allow users to sign up checkbox
Under Authorization, choose Project-based Matrix Authorization Strategy
Add first user with the name admin and another with GitHub (Note: the username for Admin access has to be admin) For GitHub named user, just choose the Overall Read only permission. We’ll use this user later with the GitHub hook.
Note: The admin and GitHub user that we’ve added in the above step does not create the User. Then you’ve to create a real user with that same name. Ya, I know, its a bit weird with Jenkins UI.
Go to Manage Jenkins > Manage Users > Create User. Create both admin and GitHub users.
Hooking with the Github web-hooks
Now to run the build automagically when new commit or branch gets pushed onto Github, we have to setup the repository.
Got to the hooks page for your repository. e.g.
github.com/<username>/<project_name>/admin/hooks
Under AVAILABLE SERVICE HOOKS > Post-Receive URLs, add github:github#your-ci-server.com/github-webhook/.
The github:github is the user that we’d created earlier.
Then we have to verify Jenkins with Github. Go to Manage Jenkins > Configure System and under GitHub Web Hook, add your Github username and password and click the Test Credential button to authorize once with Github.
It looks like the accepted answer is no longer necessary with the current version of the GitHub plugin. You can instead check Grant READ permissions for /github-webhook in "Configure Jenkins" under the GitHub plugin settings, allowing the webhook to be called without authentication.
As explained in the help on this option that's quite safe, and frankly no worse than having a user named "github" with password "github" anyway.
There are two ways to achieve automatic builds on Jenkins. What you choose depends on whether GitHub can call the Jenkins server URL you provide. This may not be the case if you are running Jenkins behind a firewall.
If GitHub can reach that URL you can set up the service hook on your repo there.
If not you can set up Jenkins to poll periodically.
You may set up both, but one solution is enough to get it working. I would always go for the first if feasible as it saves resources CPU and traffic wise.
Either way you need the GitHub plugin for Jenkins.
Hope that helps a bit.