Closed Bug 1458622 Opened 8 years ago Closed 6 years ago

Enable jenkins for the security repository

Categories

(addons.mozilla.org :: Security, enhancement)

Product:
addons.mozilla.org
Component:
Security
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: TheOne, Unassigned)

References

Details

It would be great if we could add a job to jenkins to be able to push directly to stage/prod from that repository, in order to avoid having to commit the patch to the public repo before deploying.
This seems like it can be done, it would require a change in the dev workflow as the tag would need to be made in the security repository. There are some things to work out on then Jenkins side to make sure that the automation works out properly.
Flags: needinfo?(scolville)

Give that this is something that comes up relatively infrequently, and after giving this some thought - I'm going to mark this a wontfix. If this becomes more frequent or there's greater need for it in the future then let's reopen it.

Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(scolville)
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.