Is there a way, where gitlab new sorftware versions, environmental changes(IP, auth), and testing bugs can be displayed automatically in Jira or Confluence? Basicly a unified page where all changes could be tracked would be useful.
My general idea of a page is like a three column page:
Environment 1:
current version per each app | environment address and auth | jira highest priority bugs
Environment 2:
current version per each app | environment address and auth | jira highest priority bugs
Environment 3:
current version per each app | environment address and auth | jira highest priority bugs
So now, at my company, all of the above are spread all across the different apps and pages and issues. It is time consuming and a hassle to login and, load all pages all the time.
Different pages we now use:
Gitlab branches
Confluence environment page
Jira testing bugs
Related
Currently I am working in a project where we have 8 instances accross different geographies. We currently use bmc rlm ( https://docs.bmc.com/docs/ReleaseLifecycleMgt/50 ) for deployment automation.
However to keep track of our deployment ids we are using excel.
Starting from Dev environment , to QA environment ( each region has
its own QA and schedule ) and ultimately move to Production.
What I wanted to know was , is there any tool that you use to keep
track of deployments ?
We tried using sharepoint but it is kind of limiting in the features.
We would ideally like a workflow to be created , whereby developers
submit the request with the dev deployment id.
Workflow goes to Release Approver for QA env. Once he/she approves ,
QA testing team gets notified.
Please let us know if anybody else faced this kind of issue and used some tools for the same?
We have recently started public preview of Reliza Hub https://relizahub.com which aims to solve this problem.
Some of the functionality you are asking (particularly approvals) is not there yet, but it's coming. Tracking functionality and mapping instance to releases is there already.
Currently I'm trying to add documentation as we go, so far Version Increment workflow is documented here. And functionality to send release data to Reliza Hub is documented in our client github.
Would be happy to provide support and discuss incomplete or missing features via our new reddit channel r/Reliza.
I have two projects in JIRA: software project and service desk project.
My goal it to enable my service desk customers to access the software project but in a limited way. E.g.:
clients could create stories,
comment on them,
assign priorities
and assist with assigning them to iterations / releases.
But they would not be able to perform and see some actions e.g.:
see the logged time
and ideally to keep some of the ticket / story fields and comments as internal use only so I can have technical discussions with my team without the client seeing them etc.
I can see in documentation that "Service Desk Customers can't log in to JIRA applications":
https://confluence.atlassian.com/servicedeskcloud/setting-up-service-desk-users-732528877.html
But is there any workaround to give Service Desk Customers access to JIRA applications? Is there any simpler method than making a REST API bind? If yes, then how it could be achieved?
The documentation is not clear. Add their accounts to the jira-users group and they will be able to log into JIRA as regular users. The point is that member of jira-users consumes a JIRA user license, while "pure" customer account does not.
As regular regular users they will have permissions just as you configure your project Permission Scheme, so everything is in your hands. Using roles you can restrict issue comments to those roles. There's also nice Comment Security Default plugin to use with that.
Is it correct that I can see the project "Dataflow: Readonly Artifacts (DO NOT DELETE)" in my developers console? Ever since I got alpha access to CDF last month, it has been visible.
I also noticed that I got charged on the project even before we started to test and run jobs (which was literally just a few hours ago!). My understanding is that CDF is free in alpha, but that you must pay for any services used e.g. BigQuery, GCS etc. However, I would expect those charges to show up in my other project because I specify that project name/id when actually creating the PipeLine.
Those charges are not assessed to you as a Dataflow user -- they are charged to the project owner, which is the Cloud Dataflow team. As part of whitelisting for Dataflow, you've been granted read-only access to the project to allow you to access specific artifacts during Alpha (such as the custom GCE image for Dataflow).
the problem i have is i have two different teams.
team 1 : support 800 applications
team 2 : 400 application
i want them on jenkins , but i want to keep there jobs seperate so team 1 can only see there jobs , while team 2 can only see there jobs.
is there where i can have one jenkins instance and then two slaves ? where one slave see only team 1 applications jobs, and slave 2 sees only team 2 application jobs. ?
any suggestion to which direction i can start looking into will help.
any plug in i can look at ?
I don't think a slave will do what you want. You are trying to control who can see the jobs. You could configure certain slaves to run certain jobs, but all jobs are still viewable through master.
Take a look at the Folders plugin. You can give each team a folder and separate access so they can only see the folder for their team.
#adam,
Same answer to your other question.
Use Jenkins Role Strategy Plugin.
This plugin adds a new role-based strategy to ease and fasten users
management. This strategy allows:
Creating global roles, such as admin, job creator, anonymous, etc., allowing to set Overall, Slave, Job, Run, View and SCM permissions on
a global basis.
Creating project roles, allowing to set only Job and Run permissions on a project basis.
Creating slave roles, allowing to set node-related permissions.
Assigning these roles to users.
Hope that helps.
JIRA upgrade from 4.0.x to JIRA 5.1.3 - will the same running license work?
Jira licence includes 12 months of maintenance (updates/support) , during that time you can update for free without purchasing a new licence. After those 12 months you can use your Jira freely, but you cannot upgrade it. To learn more have a look at the Jira's licensing information.
A JIRA commercial/academic license entitles you to: (as for Jira 5.0)
Deploy a single instance of JIRA in a production environment on 1 server
Unlimited projects and issues
Perpetual JIRA use
Software maintenance for 12 months - including all updates and online support (from Sydney, Australia and San Francisco, USA during local business hours)
Full source code (under a developer source license which allows for broad customization)
Licensing fees are quoted per number of 'active users'. An active user in JIRA is by definition any user account in the system with the "JIRA Users" global permission, i.e. anyone who can log in. Unlimited 'anonymous users' are permitted on all licenses.