In this blog, I am creating the transitions and transforms in image tags using HTML & CSS. So, Let’s create an index.html & style.css below-
Different ways to write the transitions and transforms in image tag using HTML & CSS. Part-2
Tag: Ways
Limited Time Offer!
For Less Than the Cost of a Starbucks Coffee, Access All DevOpsSchool Videos on YouTube Unlimitedly.
Master DevOps, SRE, DevSecOps Skills!
Different ways to write animation, transitions, and transforms in button tag using HTML & CSS.
In this blog, I am creating Different ways to write animation, transitions, and transforms in button tags using HTML & CSS. So, Let’s create an index.html & style.css below-
Different ways to write the transitions and transforms in image tag using HTML & CSS.
In this blog, I am creating the transitions and transforms in image tags using HTML & CSS. So, Let’s create an index.html & style.css below-
Different ways to write the transitions in any tag or button using HTML & CSS.
In this blog, I am creating different transitions in buttons & div using HTML & CSS. So, Let’s create an index.html & style.css below-
In, this index.html multiple div, tag with multiple class which is defined below style.css-
In, this style.css I am used multiple classes with multiple functionalities as color, padding, margin, opacity, width & height. When you using this index.html & style.css then shows below image-
Below is one more index.html for transitions hover property-
Below is style.css for the used upper index.html –
button { height: 90px; width: 290px; font-size: 28px; color: white; border: none; background-color: blue; transition: all 3s ease-in 2s } button:hover { background-color: green; color: black; border-radius: 50%; }When you used index.html & style.css then show below-
How many ways are there to add JavaScript?
Way of adding JavaScript:
Inline–
- Inside head Tag
- Inside body Tag
Inside Head Tag
Inside Body Tag
External file
- Inside head Tag
- Inside body Tag
Inside head Tag
Inside body Tag
- <script> – Opening Script Tag.
- src – It‟s an attribute of script tag. It defines source/location of script file.
• dev.js – This is our script file. Where dev is file name and .js is the extension
of javascript file.
• type – It‟s an attribute of script tag which tells the browser it is a javascript.
This is optional now a days.
• text/javascript – Its type of document
• document.write(“Hello World”); – This is a function to display data.
• </script> Closing Script tag
How to attach the jenkins build log as part of the email body?
Way 1 –
Put following lines as part of Default Content text box
${BUILD_LOG, maxLines=9999, escapeHtml=false}
this works for free style projects
Way 2 – If you want send only specific line using regex
${BUILD_LOG_REGEX, regex=”\\b(Buildfile|BUILD)\\
${BUILD_LOG_REGEX, regex=”^.*?BUILD FAILED.*?$”, linesBefore=0, linesAfter=10, maxMatches=5, showTruncatedLines=false, escapeHtml=true}
${BUILD_LOG_REGEX, regex=”\\b(FC0)\\b”, linesAfter=1}
${BUILD_LOG_REGEX, regex=”^.*?BUILD FAILED.*?$”, linesBefore=0, linesAfter=10, maxMatches=5, showTruncatedLines=false, escapeHtml=true}
${BUILD_LOG_REGEX, regex=”^.*?FC0.*?$”, maxMatches=95, showTruncatedLines=false, escapeHtml=false, matchedLineHtmlStyle=true}
This will show exactly which is expected lines as part of the regEx.
List of other variables as part of email body
${PROJECT_URL}/ws/
${BUILD_URL}/artifact/
${BUILD_LOG, maxLines=1000}
More ref
Content Token Reference
In string arguments, escape “, \, and line terminators (\n or \r\n) with a \, e.g. arg1=”\”quoted\””; arg2=”c:\\path”; and arg3=”one\ntwo”. The brackets may be omitted if there are no arguments.
New Lines – Use <br> or “\”
More Info
How to attach the jenkins build log as part of the email body?
Way 1 –
Put following lines as part of Default Content text box
${BUILD_LOG, maxLines=9999, escapeHtml=false}
this works for free style projects
Way 2 – If you want send only specific line using regex
${BUILD_LOG_REGEX, regex=”\\b(Buildfile|BUILD)\\b”, linesAfter=1}
${BUILD_LOG_REGEX, regex=”^.*?BUILD FAILED.*?$”, linesBefore=0, linesAfter=10, maxMatches=5, showTruncatedLines=false, escapeHtml=true}
${BUILD_LOG_REGEX, regex=”\\b(FC0)\\b”, linesAfter=1}
${BUILD_LOG_REGEX, regex=”^.*?BUILD FAILED.*?$”, linesBefore=0, linesAfter=10, maxMatches=5, showTruncatedLines=false, escapeHtml=true}
${BUILD_LOG_REGEX, regex=”^.*?FC0.*?$”, maxMatches=95, showTruncatedLines=false, escapeHtml=false, matchedLineHtmlStyle=true}
This will show exactly which is expected lines as part of the regEx.
More Info
http://wiki.hudson-ci.org/display/HUDSON/Email-ext+plugin
http://champasoft.blogspot.nl/2012/11/jenkins-pattern-for-e-mailing-log.html
Source code analysis tools: Evaluation criteria
Source code analysis tools: Evaluation criteria
Support for the programming languages you use. Some companies support mobile devices, while others concentrate on enterprise languages like Java, .Net, C, C++ and even Cobol.
Good bug-finding performance, using a proof of concept assessment. Hint: Use an older build of code you had issues with and see how well the product catches bugs you had to find manually. Look for both thoroughness and accuracy. Fewer false positives means less manual work.
Internal knowledge bases that provide descriptions of vulnerabilities and remediation information. Test for easy access and cross-referencing to discovered findings.
Tight integration with your development platforms. Long-term, you’ll likely want developers to incorporate security analysis into their daily routines.
A robust finding-suppression mechanism to prevent false positives from reoccurring once you’ve verified them as a non-issue.
Ability to easily define additional rules so the tool can enforce internal coding policies.
A centralized reporting component if you have a large team of developers and managers who want access to findings, trending and overview reporting
Jenkins Command line Reference for login and trigger a job
Grep will return 0 while the build is running:
$ curl http://myjenkins/job/myjob/lastBuild/api/json | grep –color result\”:null
$ echo $?
Trigger a Jenkins Job from command line
$ wget http://yourserver/job/MyJobname/build?delay=0sec
$ wget -O – $HUDSON_URL/job/JOBNAME/build
Trigger a Jenkins Job without authentication
$ curl http://jenkins:8080/job/my%20job/build
Trigger a Jenkins Job with authentication
$ curl –user dbacher:$MY_API_TOKEN http://jenkins:8080/job/my%20job/build
$ curl –user <your_jenkins_username>:<your_jenkins_API_key> http://<jenkins_server_url>/job/<your_jenkins_job_name>/build
Running commands against a secure Jenkins (basic auth or ssh keys)
$ java -jar jenkins-cli.jar -s http://myjenkins help –username me –password mypassword
$ java -jar jenkins-cli.jar -s http://myjenkins help -i ~/.ssh/id_rsa
Triggering a job build against a secure Jenkins (avoiding a 1.5 year old open bug!)
$ java -jar jenkins-cli.jar -s http://myjenkins build ‘My Awesome Jenkins Job’ -i ~/.ssh/id_rsa
$ java -jar jenkins-cli.jar -s http://myjenkins build ‘My Awesome Jenkins Job’ -i ~/.ssh/id_rsa -s -v
Passing parameters when triggering a job build
$ java -jar jenkins-cli.jar -s http://myjenkins build ‘Deploy XYZ App’ -i ~/.ssh/id_rsa -s -v -p target_env=api.cloudfoundry.com -p branch=master
Reference
http://starkandwayne.com/articles/2013/04/12/jenkins-builds-from-cli/
Appendix
1. How to get your_jenkins_API_key?
- Login to your Jenkins.
- Click on the username in the top right.
- Click on Configure.
- Click on ‘Show API Token’ button.
- You got it.
Step by Step Instruction to Upgrade Perforce to 2014
Step by Step Instruction to Upgrade Perforce to 2014
The step are as follows:
a) Check if the license is current.
p4 license -o
The expiry date must be later than the binary release date you are installing
b) Verify server archives using the command ‘p4 verify -q //… > verify.txt’
* Note – If the file ‘verify.txt’ contains a ‘BAD!’ or MISSING!’
signature during the verify command, please contact Perforce Support prior to upgrading.
** If the depot is large and you get an error message “Request too large for server memory”, you can split the verify to check chink of the depot:
Example:
p4 verify -q //depot/project1/… > prj1-verify.txt
p4 verify -q //depot/project2/… > prj2-verify.txt
p4 verify -q //depot/project3/… > prj3-verify.txt
c) Stop the Perforce Server.
p4 admin stop
d) Make a checkpoint of the database.
p4d -r P4ROOT -J journal -jc
e) Copy the db.* files to a safe location.
f) Backup your archive files.
g) Read the release notes so you are aware of the latest changes.
http://www.perforce.com/perforce/doc.current/user/relnotes.txt
h) Download the latest P4D version.
ftp://ftp.perforce.com/perforce/
i) Verify that the newly downloaded binary is the latest. You might need to copy the p4d.exe to p4s.exe
p4d.exe -V
p4s.exe -V
j) Install the upgraded version of the Perforce server.
k) Restore the Perforce Server using the new P4D Binary and the checkpoint taken from the old P4D binary, with the following command ‘p4d –r root –jr checkpoint.xxx’.
l) If the server contains more than 1000 changelists, please run the following command ‘p4d -r root -xu’ from the command line’.
m) Start the perforce Sever.
n) Verify server archive files.
p4 verify -q //… > upgrade-verify.txt
** Note – If the file ‘upgrade-verify.txt’ will contains a ‘BAD!’ or MISSING!’ signature during the verify command, please contact us.
o) Take a checkpoint
p4d -r root -J journal -jc
This is also explained in the below article:
Upgrading to 2013.3 and beyond – http://answers.perforce.com/articles/KB_Article/Upgrading-to-2013-3-and-beyond
Windows To Linux
Moving from Linux to Windows is not a trivial issue, and such a migration is also not supported and will most likely require consolidation of case sensitivity conflicts using our P4 Migrate product. Please see the link below:
Cross-Server Platform Migration
http://answers.perforce.com/articles/KB_Article/Cross-Platform-Perforce-Server-Migration/?q=linux+to+windows&l=en_US&fs=Search&pn=1
http://answers.perforce.com/articles/KB_Article/Cross-Platform-Perforce-Server-Migration
Change of Server is a “Self-serve” option, please fill out this form and licensing will update accordingly.
P4 Support Change of Server License Request
http://www.perforce.com/support-services/change-server-request
Please pass the -z switch during the replay as the checkpoint/journal you are replaying are compressed:
p4d -r P4ROOT -jr -z checkpoint.ckp.104.gz
You will need to request for a background user I believe to be able to do all the required command. This can be done by filling in this below form and using one background user for all of you build machines.
http://www.perforce.com/support-services/request-background-user
Moving a Perforce Server
http://answers.perforce.com/articles/KB_Article/Moving-a-Perforce-Server
By Chris Lesemann <support@perforce.com
Our Knowledge Base has accurate and up to date information that will help you prepare your own procedure for upgrading. Because the database structures have changed, you will need to take an existing checkpoint and then replay that checkpoint with the 2014.1 version of the P4 Server.
It appear you are on a 32-bit Windows instance…will you be doing an inplace upgrade or moving to 64-bit hardware? If you are moving from 32-bit to -64bit you have to recover from checkpoint anyway.
Please review the two links below and if you have any further questions I would be happy to assist you:
Upgrading to 2013.3 and beyond <– specific procedure for moving from 2013.2 and earlier P4 to 2013.3 and later
Upgrading a Perforce Server <– in-place upgrade
Moving a Perforce Server <– if you have to move to new hard – do NOT start a 64-bit P4D binary against 32-bit db.* databases, or vice versa.
General information on the new Btree structures and functionality:
BTree Format Changed for Perforce Server Versions 2013.3 and Later