Helix SwarmHelix Swarm
Loading...

karl_wirth

  • //
  • guest/
  • karl_wirth
  • Browse
  • Commits
  • Download .zip
Name Modified Size
..
example_scripts
Nagios
TempFiles
Change User Description Committed
21552 Karl Wirth Adding a test MD file 8 years ago
21509 Karl Wirth Simple example Groovy formatter for formatting Jenkins snippets.
Expects data passed thro...ugh stdin. Outputs results to stdout. «		 8 years ago
18844 Karl Wirth Minor bug fix and more doc updates:
- Tests 27 (Replication Fail - journal missing) inter...mitantly failing due to timing issues with replication. Change test to use 'p4d -cset' instead of 'p4 configure set'.
- Test harness section added to README.md . «		 9 years ago
18843 Karl Wirth Updated tests with a backwards compatible checkpoint.
Tests can now be run with P4D back... to 2012.2.

Thanks @dale_sumbler for the QA. «		 9 years ago
18842 Karl Wirth Updates to documentation and minor bug fixes. 9 years ago
18841 Karl Wirth Updating test script:
- minor bug fixes.
- comment block.
- check for P4Nagios existance... and executable.
- change filetype to ktext. «		 9 years ago
18835 Karl Wirth Further tidying up and addition of test suite.
       - refactored p4... commands
       - extra error trapping
       - fix numerous bugs
       - added perl based test suite and reference checkpoint
       - created new banner
       - updated README to match current params «		 9 years ago
18814 Karl Wirth Deleting original test script so that it doesnt get published. 9 years ago
18813 Karl Wirth The original test script written in bash that does not meet Nagios plugin standards.


... Submitting just in case I need to revert back to it. «		 9 years ago
18801 Karl Wirth Refactoring, tidying up and results of further testing:
       - Impr...ovements to replication checking (uses p4 pull -lj)
              - Long opts for all test related arguments
       - Security enhancements (P4TRUST and P4TICKETS files)
       - Variable standardisation
              - Tabs replaced with spaces
              - Make Nagios happy when no problems found
              - Extra Perforce user and P4 command feedback checking
              - New flags
               --message to provide custom messages.
               --remote to allow script to be run remotely (from Nagios server)
               --notip to hide tips if they get to annoying

TBD - Check for replication slow down.

       Documentation updated to match code. «		 9 years ago
18711 Karl Wirth Adding an update to the alpha version that:
       - checks disk spac...e.
       - checks p4 monitor output.
       - check replication status.
       - P4 binary exists and is executable.
       - standardises on paramater names.

Documentation updated with latest changes.

To Do: Tidy up, adherence to coding standards and further testing. «		 9 years ago
18657 Karl Wirth Adding a readme for this temp directory. 9 years ago
18656 Karl Wirth added 9 years ago
18303 Karl Wirth Adding missing image 9 years ago
18302 Karl Wirth Fixing formatting problems with the README.md 9 years ago
18294 Karl Wirth Alpha version of an example Nagios plugin for the Helix P4D server
and related documentat...ion. The intention is to complete this by
adding additional checks and error handling then add scripts for
Git Fusion, Swarm and GitSwarm. «		 9 years ago
10812 Karl Wirth P4DTG JIRA 6.X clickable URL proof of concept

           ... Adding an example trigger script that will populate a job field with
            any attached changelists in WIKI format. This could be replicacted to
            JIRA 6.X which has the ability to render custom fields in WIKI format
            making text (in this case changelist number and revision) clickable.

            From top of file:

            # Description:
            # Example trigger script to write changelist and list of files that fixed job to a
            # job field so they can be copied to JIRA by P4DTG. If this feeld is configured
            # to render using the 'WIKI style' renderer. More information on this can be
            # found in:
            #    https://confluence.atlassian.com/display/JIRA/Configuring+Renderers
            #
            # Important Note:
            # This is only an example script to demonstrate how you could use P4DTG to
            # replicate data and have it displayed as an active URL to p4web in JIRA.
            # It has not been tested and is not ready to be installed in a production
            # environment.
            #
            # Example usage:
            # (1) Create a custom Text field in the Perforce jobspec.
            #       135 P4WebURLS text 0 optional
            # 
            # (2) Create a custom 'Free Text Field (unlimited text)' in JIRA and configure
            #     it to render with a custom renderer.
            #
            # (3) Modify 'jira-config.xml' and set the JIRA custom field to be
            #     type 'TEXT'. For example:
            #        <CustomField name="CustomTextField" type="TEXT" access="RW" />
            #
            # (4) Use P4DTG-Config to 'Check Connection' to the JIRA source, click
            #     'Apply' then map P4WebURLS-->CustomTextField.
            #
            # (5) Test the trigger at the command line by output a job that has fixes
            #     to a text file, then running the script against this file. For
            #     example:
            #        p4 job -o job001234 > tmp.txt
            #        perl jira6_p4web_url_trigger.pl tmp.txt job001234
            #     After running the script 'tmp.txt' should contain the change and list
            #     of files in P4Web URL format.
            #
            # (6) Modify the environment section below to match your Perforce and
            #     P4Web settings.
            #
            # (7) Creat a 'form-out' trigger definition for the script.
            #     Triggers:
            #        jira form-out job "perl ./jira6_p4web_url_trigger.pl %formfile% %formname%"
            #
            #
            #=====================================================================================
            #
            # EDIT THIS SECTION TO MATCH YOUR ENVIRONMENT
            #
            #=====================================================================================

            # Define location of P4 binary
            # $p4 = "C:\\Program Files\\Perforce\\p4.exe";
            $p4 = "/usr/local/bin/p4";

            # Define Perforce connection details
            $p4user ="test";
            $p4password = "Password";
            $p4port = "localhost:6789";
            $p4client = "test_ws";

            # Define job field to contain URLS (must be in jobspec)
            $urljobfield="P4WebURLS";

            # Define P4WEB server name
            $p4weburl = http://localhost:1234/

            # Set debugging on (0=off,1=On)
            $debug=0;

            #===================================================================================== «		 10 years ago