I'm using open source puppet version 3.8 to control my environment in AWS.
I was wondering if there is good way to monitor puppet agents failures.
basically, I would like to get notified by email each time a puppet run fails (for each node).
is there a way to achieve this functionality in the open source version of puppet?
any help would be appreciated.
I'd recomend the tagmail module for this: https://forge.puppet.com/puppetlabs/tagmail
"Puppet's loglevels (debug, info, notice, warning, err, alert, emerg, crit, and verbose) can also be used as tags, and the all tag always matches every log message."
You could also setup to tag on particular resources or classes, depending on when you want the error messages to show.
Related
I set up a workspace and I am following the Enforce Policy with Sentinel hands on guide.
I see the following message in the run tab:
As soon as I try to press the queue plan button I receive this error:
My configured variables are:
Is there something else I need to configure to be able to queue a plan?
Executing from the cli I was able to trigger a run (in TF Cloud) that only included the plan step. The run execution can be viewed if I access the specific run url directly.
Any help, suggestions are more than welcome!
I guess you've already resolved this issue, but I post my resolution anyway.
When this issue occurred, I had wrong workspace's name settings.
There were two workspaces with similar names, and I don't know why this happened. Then I deleted one of them.
On the other one occurred this issue.
In the end, when I deleted the workspace and recreated it, I didn't have the issue occurring anymore.
In my case I didn't have duplicate / similar names workspaces (only one workspace). I found that after running terraform apply locally once first, the UI controls started to work as expected.
How do you access current, and related, build information from within a Jenkins workflow groovy script?
I can see things like currentBuild.result and currentBuild.previousBuild being documented, but I can't see how I can access, for example:
The URL of the current build job.
The URL of build jobs that this workflow triggered.
The console output of a particular failed build job, etc.
Thanks for any pointers.
currentBuild.rawBuild will give you the non cached hudson.model.Run object, see hudson.model.Run
from there, to access i.e. the build log:
def buildLog = currentBuild.rawBuild.log
currentBuild.rawBuild is also of type hudson.model.AbstractBuild which can give you other details like changeset, actions
i have gitlab omnibus, 8.0.4 version, installed on private server, we need to remove access right from reporter to read/pull/download code,
so we dont want reporter to viewer the source code
I think it can be done through editing some file on the server, right?
how can we do it?
Reporter always has read access to files, issues and merge requests. This cannot be altered (and we do not recommend modifying source files since it makes upgrades more difficult).
My suggestion is to create a separate project with only the issue tracker enabled and add the user as a reporter there. Keep the project with source code private.
Danger section ;)
If you really want to modify the code, look in app/models/ability.rb. In the project_report_rules method remove the rights you do not wish 'reporter' to have.
This question made me crazy!Please help me.
I use the buildbot, VC tool is perforce 2010.
Waterfall: ok
but console view cannot work right.
just print "No revisions available"
If you are using the Periodic scheduler, then buildbot isn't made aware of the revisions in your repository, it just checks every time, and builds the most recent version. Since it doesn't know anything about revisions, it can't display anything sensible for the console view.
To get the console view, you need to tell buildbot about your revisions, either using buildbot.changes.p4poller.P4Source, buildbot send-change or contrib/post-build-request.py. And then trigger your builds using a regular scheduler, rather than a periodic one.
It's probably something environmental in the configuration, such as the Perforce username or the Perforce client spec. The tool is probably issuing a 'changes' or 'sync' command, and since it's not using the workspace definition that you expect, it isn't finding any code in that workspace.
I was wondering if it is possible if I could include a Fix List with my deployment build email notification,what I was expecting is I would add the latest changes to a text file stored in a directory and CruiseControl.NET would pick it from there and send along with the email.Anybody has any similar solutions, or how did you do it? Any samples or links?
Thanks in advance.
The first question is whether you do continuous integration (CI) builds or just periodical builds? In case it is CI, have you tried writing this fix list into the check-in comment of your version control system? CCNet shows this comment as part of the build report (and email notification).
UPDATE: the other option I see is to write your own CCNet plugin for this. It shouldn't be too hard. As a reference on writing CCNet plugins you can use my own BrekiLabeller plugin.