Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #9961] Don't re-download NSCP for every build #3298

Closed
icinga-migration opened this issue Aug 18, 2015 · 2 comments
Closed

[dev.icinga.com #9961] Don't re-download NSCP for every build #3298

icinga-migration opened this issue Aug 18, 2015 · 2 comments
Labels
Milestone

Comments

@icinga-migration
Copy link
Member

@icinga-migration icinga-migration commented Aug 18, 2015

This issue has been migrated from Redmine: https://dev.icinga.com/issues/9961

Created by gbeutner on 2015-08-18 18:12:47 +00:00

Assignee: gbeutner
Status: Resolved (closed on 2015-08-18 18:50:02 +00:00)
Target Version: 2.3.9
Last Update: 2015-08-24 11:39:09 +00:00 (in Redmine)

Icinga Version: 2.3.8
Backport?: Already backported
Include in Changelog: 1

Changesets

2015-08-18 18:16:22 +00:00 by (unknown) 854f8ec

Don't re-download NSCP for every build

fixes #9961

2015-08-24 11:38:55 +00:00 by (unknown) c298261

Don't re-download NSCP for every build

fixes #9961
@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Aug 18, 2015

Updated by Anonymous on 2015-08-18 18:50:02 +00:00

  • Status changed from Assigned to Resolved
  • Done % changed from 0 to 100

Applied in changeset 854f8ec.

@icinga-migration

This comment has been minimized.

Copy link
Member Author

@icinga-migration icinga-migration commented Aug 24, 2015

Updated by gbeutner on 2015-08-24 11:39:09 +00:00

  • Target Version changed from 2.4.0 to 2.3.9
  • Backport? changed from TBD to Yes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.