Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Add support of secrets and credentials in Standard-CI

Description

Some task we'd like to carry out in Standard-CI require credentials. Examples for such tasks include:

  1. Publishing artifacts to repositories (E.g containers to Dokcerhub, puppet code to Puppetmaster)

  2. Launching remote processes (Check code with remote services)

While Jenkins supports storing and managing secret data, we did not enable a way to use this capability from Standard-CI so far.

Activity

Show:

Former user October 8, 2017 at 9:25 AM

I'll close this ticket as the core feature is working. I'll open a new ticket to track your comments here

Barak Korren October 8, 2017 at 8:38 AM

Please update this ticket to indicate current status, as main patch has been merged.

Added a patch with an example configuration file.

Error messages in code written for this ticket need to be improved:

  • All references to things like 'xdg-home' need to be replaces with specifications of actual paths, as users are not expected to know what XDG is.

  • Accurate indication of what is missing from which file and what can be done to fix it need to be given in all error messages.

  • When variable/key names are given in error messages, they need to be quoted for clarity.

  • Edge cases like for example an existing but empty secrets file and a missing 'secrets_data' key need to be handled better, with clear error messages.

Former user July 13, 2017 at 1:04 PM

Moving back to To Do and reducing priority as it seems that I don't get to resume the work on this ticket for now.

Former user July 12, 2017 at 10:58 AM

yes, we just have more urgent tasks right now.

Eyal Edri July 12, 2017 at 9:37 AM

is this really in progress? latest patch is from 9 weeks ago

Fixed

Details

Assignee

Reporter

Blocked By

Components

Priority

Parent

Created December 1, 2016 at 10:00 AM
Updated November 1, 2017 at 10:03 AM
Resolved October 8, 2017 at 10:02 AM