Limited Time Offer!

For Less Than the Cost of a Starbucks Coffee, Access All DevOpsSchool Videos on YouTube Unlimitedly.
Master DevOps, SRE, DevSecOps Skills!

Enroll Now

How to set up a Jira cloud instance?

Hi dears, welcome to the course study of Jira. Today, through this article, I will explain to you how you will set up a Jira instance so that you can start to use Jira software for your projects. I have miscellaneous agenda for you. On which topics you will learn is types of Jira instance, what is the difference between server and Cloud instance? And how to create a cloud instance of Jira? So, let’s move forward to learn more about Jira concepts

Jira instance

Basically, there are two types of Jira instances, the first one is cloud and the second one is server. I will tell you what is the difference between the cloud and server instances and which one you should use if you are a beginner to learn about the Jira software. So, let’s move forward to learn about the cloud and the server instances.

Cloud vs server instance

Here I will discuss the cloud instance first. So, what is a cloud instance? In the cloud instance rather than installing and maintaining, your product on your own server Atlas Sian host and set up your Jira application on the cloud for you so, this is the cloud instance and according to me, this is the best instance for the beginner, who want to learn from the very beginning. It is very fast because it’s easy to set up and get started in minutes as soon as you sign up. You may start working and inviting the team members and the second one is reduced costs because it helps to save money on the physical hardware maintenance installation support and any other hidden administration cost as well. This is a cloud instance so, everything is on the cloud and there is no need to bear the cost of your own hardware. The third one is no need to upgrade because on the cloud you get immediate access to the latest version on Jira so, there is no need to upgrade the cloud instance. The fourth one is security, it is very secure because atlas Sian takes the responsibility to maintain the security and compliances of your data and organization so, I describe the benefits of the cloud instances but I want to tell you one more thing about you don’t have direct access to change the database structure, file system, or other server infrastructure because you have a cloud instance and atlas Sian already set up your cloud instance. So, they will not give you administrator access. Let’s learn more about the server instance. What is a server instance? In the server instance, basically, you install, host, and run the Atlas Sian’s product on your own hosting environment. So, basically, those teams will prefer that want to manage all the details on their own and are able to handle the complexity of setting up and hosting the product on their own server. So, if your organization is very big and you have a department of administrators. They can manage the administrator task of the Jira or the server so, you can go with the server version but you are working in a startup and you want to learn your own then go with a cloud one.

In this complete course, I will also use the cloud instance because as I already told you, it is very easy to set up and everyone can access it from anywhere but in the server instance may be the organization installed it on the internal environment so, you would not be able to access it from outside the organization but in the cloud instance, you may access anywhere as I told you I will explain the cloud version in this course so may be the people who are using the server one they will see some differences in the UI because the cloud and the server UI is different in the server we have the navigation on the top but in the cloud we have the navigation in the left hand side and many more other differences in the UI so as I told you the difference between the cloud and the server instances so let’s move forward and see how can you create the cloud instance of Jira so for creating the cloud instance of JIRA so, you will go to the atlas Sian website, there is an atlas Sian official website www.atlassian.com once you will click on the product tab then you can see the complete list of the atlas Sian the product but there you will go with the Jira software so, you will click on Jira software.  It will take you on that page you may try it free then you can see the three plans and there will be cloud one. You may see try the product in the cloud and that is a free 7 days trail period you can go with any of the packages so, you will go there with any of the packages and you will go there with that one so, you will click on try it free, you will say that is a 7 day free cloud trial and it will give you the full access to all features, you can add the unlimited users and access to sales and technical support so, you will create the account there so you will use your ID and you will click on agree and sign up once you will end with the sign up process then you will see the screen where they will ask you to check your inbox and confirm your email ID so, you will go to your email so to verify that email you will click yes verify and it will redirect to you to the page if you want to select what type of team with do you work in then you can but for that you will skip and see the URL there that is a JIRA all sort of gentle that you have mentioned at the time of creating the account and you can invite your team with the help of the email address if you will enter the email address there and send the invitation then the people will get the email will get the invite and they can accept and use this environment and that JIRA instance for now you will skip that  and there they will ask are you new to Jira or are you already experienced with Jira then you can find out for now. That will be the next page where you can see there are the two types of templates are available first one is the classic template and the second one is a next-generation template. You can see there the Kanban is scrum and the bug tracking three templates are available and these three templates come under the software category so if you will go and will select all types you can see there are many more templates are available which are related to business. In this course, that’s it for today this is a process where you can create the cloud instance.

Related video:

 

Tagged : / / / / / / / / /

php version (7.2.34) does not satisfy that requirement.

When i download the Laravel project from Github and setup project i run composer update its showing this types of error

Problem 1
- Root composer.json requires php ^7.3|^8.0 but your php version (7.2.34) does not satisfy that requirement.
Problem 2
- phpro/grumphp[v1.0.0, ..., v1.1.0] require php ^7.3 -> your php version (7.2.34) does not satisfy that requirement.
- phpro/grumphp[v1.2.0, ..., v1.3.1] require php ^7.3 || ^8.0 -> your php version (7.2.34) does not satisfy that requirement.
- Root composer.json requires phpro/grumphp ^1.0 -> satisfiable by phpro/grumphp[v1.0.0, ..., v1.3.1].

Let open editor and run below

composer install --ignore-platform-reqs

Thanks

Tagged : / / /

Perforce client version numbers v99999

rajeshkumar created the topic: Perforce client version numbers v99999
The mystery v99999 is an artifact of how older releases of the p4 command line client set the protocol level. In the code, it looked something like this:

client.SetProtocol( “api”, “99999” );

In the absence of better version information, the server logs the API protocol level, or if that’s not set, the client protocol level. Since 2004.2 p4 always sets the API level to 99999, so it’s a version of p4 that was built after that, but before they introduced an explicit version string (2005.2). So basically if you see v99999 it’s either a 2004.2, or 2005.1 p4.

reference:
kb.perforce.com/article/512
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Interview Questions and Answer for Perforce Version Control Tool

perforce-interview-questions-answers

Some of the perforce commands which is not commonly used but useful.
p4 annotate – Print file lines along with their revisions.
e.g p4 annotate file.c

How to ignore files/folder in perforce workspace/client?
Assuming you have a client named “CLIENT”, a directory named “foo” (located at your project root), and you wish to ignore all .dll files in that directory tree, you can add the following lines to your workspace view to accomplish this:

-//depot/foo/*.dll //CLIENT/foo/*.dll
-//depot/foo/…/*.dll //CLIENT/foo/…/*.dll

The first line removes them from the directory “foo” and the second line removes them from all sub directories. Now, when you ‘Reconcile Offline Work…’, all the .dll files will be moved into “Excluded Files” folders at the bottom of the folder diff display. They will be out of your way, but can still view and manipulate them if you really need to.

You can also do it another way, which will reduce your “Excluded Files” folder to just one, but you won’t be able to manipulate any of the files it contains because the path will be corrupt (but if you just want them out of your way, it doesn’t matter).

-//depot/foo.../*.dll //CLIENT/foo.../*.dll

Reference
How can I exclude a directory from a Perforce command?

P4IGNORE
Specify a file that contains a list of files to ignore when adding files to the depot and reconciling workspaces.
Reference

How to check last 10 submitted, pending, or shelved changelists that include any file under the project directory?
p4 changes -m 5 //depot/project/…

How to check last 10 submitted or pending, or shelved changelists that include any file under the project directory?
p4 changes -m 1 -s submitted | pending | shelved

Interview Questions Related to Perforce Admin

  1. How to take perforce backup
  2. How to restore perforce backup
  3. How to verify health of the perforce repos database
  4. What is the ise of p4 dbverify and p4 verify

What is the use of p4 admin commands.

The p4 admin command allows Perforce superusers to perform administrative tasks even when working from a different machine than the one running the shared Perforce service.
p4 [g-opts] admin checkpoint [ -z | -Z ] [ prefix ]
p4 [g-opts] admin journal [ -z ] [ prefix ]
p4 [g-opts] admin stop
p4 [g-opts] admin restart
p4 [g-opts] admin updatespecdepot [ -a | -s type ]
p4 [g-opts] admin resetpassword -a | -u user
Reference – Click here

How to remove files from perforce permanently?
p4 archive -p with caution. This is the one of only two commands in Perforce that actually removes file data. (The other command that removes file data is p4 obliterate.)

How to set properly in Perforce?
The Perforce service offers three ways of storing metadata: counters/keys, attributes, and properties.

If your application requires only the flat storage of simple key/value pairs, and attempts to implement no security model, use the p4 counters and p4 keys commands.

The p4 property command can be used by administrators to view and update property definitions stored in the Perforce service. The service does not use the property definitions; it provides this capability for other Perforce applications, such as P4V

If your application’s metadata is associated with particular files, use p4 attribute.

If your application’s metadata is not associated with files, and if you have a requirement to restrict its visibility to users, groups, and/or to control the precedence of multiple values using sequence numbers, use p4 property.

p4 property -n name -v value
p4 counter mycounter 123
p4 key mykey 12
p4 attribute -n name [ -v value ] files…

Perforce Integration with other Tools

  1. Gitfushion
  2. Swarm
  3. Replication
Tagged : / / / / / / / / / / / / / / /

How to Select the Right Software version Control Product?

software-version-control-product

Original link: http://www.cmcrossroads.com/cm-articles/275-articles/14286-selecting-the-right-software-version-control-product

Selecting the Right Software Version Control Product Written by Mike Feighner For many years, I worked loyally for the same company where my expertise was restricted to one single software version control tool—the one that was already in place. I was not involved with determining whether the selected tool was appropriate for the company’s needs; my role was to learn it well and use it within the accepted standards, guidelines, and internally approved processes. When I recently found myself back in the job market, I realized that there were many other version control tools in use in the industry. I then began to consult with other engineers in the field and gathered data from them on which version control tools their organizations were using and the selection criteria they used in choosing a version control tool for their organization. This experience opened up a whole new world for me and soon I realized that selecting and implementing the right tools was essential for the success of any software or systems development effort. From this experience, I have drawn up a checklist of version-control-tool criteria to aid an organization in selecting the best tool. Although there are many good descriptions available on the Internet about the many tools currently on the market, I do not recommend one specific tool over the other, because some tools may fit great in one organization, but fail in another. My goal here is to suggest a partial framework for deciding which tool best fits your needs while at the same time adhering to configuration management best practices. First, you will need to define your organization’s goals, which could include any or all of the following: Good documentation should accompany your tool purchase. The tool should be portable to more than one platform. If your organization is spread out over different time zones or even across international borders, your tool should support a multi-site rather than a single-site function. The cost should be affordable. The tool should be easy to use. The tool should easily support branching and merging. The tool should have the ability to lock a file when being edited to prevent two engineers from editing the same file simultaneously. The tool should be able to accurately merge changes between two or more files. The tool should log a history of changes with notes on who made the change and why the change was made. The tool should have the ability to establish immutable baselines. Next, you will need to review your organization’s requirements for software version control and carefully review the various software tools on the market to determine which one best matches your organization’s needs. Some may be better suited for your project than others. Selecting the wrong tool can have devastating effects on your team’s effort. Lack of a good version control tool can be a major cause for delays and problems during your organization’s application development. The project will run over cost and behind schedule and can be prone to risks associated with the manual management and distribution of your project’s dependencies. Unauthorized changes and results will occur, and the customer will not be satisfied. The tool you select should not impede the implementation of configuration management best practices, which serve as a means to add value to the process, improve quality, and increase productivity. The following are some, but not all, of the questions you will need to consider. Documentation Is the tool well documented? Is support documentation available on this tool’s installation and for the tool’s use by both administrators and developers? As a reference manual, the tool’s documentation should adequately describe the tool’s features—each dialog box, tab, field, button, etc. It should answer a user’s questions about completing a specific task in a clear and concise way. Frequently, the user documentation is available in the tool’s help pull-down menu or can be downloaded electronically from the vendor’s website. Portability Is the tool portable? Can it be used on multiple platforms and operating systems? From a business perspective, your software team will be supporting a broad user market occupying various platforms, including Windows, Mac OS, or some flavor of UNIX. Your tool should be compatible on any of these platforms, as each release will simultaneously need a separate version to support each platform of your user base. Multi-site vs. Single Site Is your team located at one location site, or is your team globally distributed across the nation and across different time zones throughout the world? A “single site” constitutes one physical location such as a single building or office. A “multisite” constitutes an organization in more than one office or location in a single time zone, in multiple time zones within one country or in multiple countries. If your organization is spread out over various time zones or even across international borders, your tool should support a multi-site rather than a single-site function. A multi-site project established as a set of several individual independent single-site systems would be prone to added costs and risks associated with the manual management and distribution of the project’s dependencies. Life for a multisite organization would be a lot easier to maintain a single multisite system with access to one shared repository. A single-site organization would be wise to select a single-site system over the additional costs of a multi-site system Cost What are the costs and terms of licensing of the tool? Is it something your organization can afford? Generally, a tool designed for a large organization will have a much larger cost than one designed for a smaller organization. No one should assume paying a higher cost for your tool will solve all of your problems. Even a high cost tool may fall sort of satisfying your organization’s needs. Your decision should consider overall cost and your organization’s needs. Supporting your organization’s needs should never be underfunded. Ease of Use How easy is it to install and deploy the system? Will the tool be dependent on other tools to conduct software builds, or are some of these capabilities already an integral part of the tool? Is this a tool that is easy to use from the first day of installation throughout the entire development lifecycle? Will training and customer support be available? Will the tool require training an in-house administrator dedicated to the administration of the tool? If you are not able to immediately pick up a source code management system and start building your site, odds are it is not entirely user friendly. Ultimately, the key to a successful deployment of a source code management system is reliability and ease-of-use. A tool that is difficult to use will likely conceal the functional benefits that it would otherwise provide. If training is an affordable option for your organization, consider whether it is available through the vendor or through an unbiased third party. For a lower-cost approach in the long term, consider sending a representative from your organization to a vendor training event who will later write up a training program for your own company-based organization. Branching Does the tool accommodate branch creation? The capability to create a branch should allow duplication of an object under revision control. Thus, code modifications can happen securely in parallel along both branches at the same time whether the change involves adding a new requirement or attempting to resolve an issue from an earlier release. The tool you select should support your particular choice of branching strategy, be it by revision or release via a simple copybranch or by creating adelta branch off of the main branch or trunk. Or the tool may go a step further by creating streams that include supporting metadata and workflow automation as an enhancement in managing multiple variants in the code. Branching is one of the most important features to consider in your choice of a good source control management system as it allows you to easily support at the same time the same source code and a parallel subset of the same code being modified securely to support either a new requirement or a bugfix from an earlier release. Merging Does the tool allow merges of changes and assists in resolving conflicts between different edits to the same file? Can a merge be done via a graphical user interface or on a command line? Take into consideration that merging concurrent changes made by different developers can increase the amount of effort to resolve conflicts and achieve a merge safely. The best advice in such cases is to merge little and merge often. File Locking Does the system have a means of preventing concurrent access to the same file? Does it prevent more than one user at a time from writing to the file until the current user either checks in the file or cancels the checkout? History of Changes Does the tool maintain a log of the history of changes? Can the tool display the history of changes graphically, as in a version tree? Does the tool easily identify the current baselined version and list previous baselined versions? A history change log that maintains accurate records facilitates traceability through the code’s lifecycle, from its beginning to its eventual release and beyond. A change history log can trace a change back its origins to who made the change and to the authority who authorized the change. It plays a vital role in baselining the code. This is a basic requirement of any organization wishing to maintain proper controls and compliance. Baselining Baselining, also known as setting a control point for your code, lets you know the exact versions of all source code and other configuration items that were included in a release. Does the tool have a way of baselining the code (be it via labeling, tagging, or snapshots) to a particular version that would allow us to back out and return to the previous baselined version in the event of a problem? Is the baseline immutable? If the tool allows changes to the previously released baseline, it jeopardizes the integrity of the software. A baseline must be locked down to prevent modifications. Any subsequent release should be based on a previously release baseline. Conclusion No one software version control tool can possibly fit every organization’s needs. There is no one size fits all. The right tool should help you safeguard your code and help your process improve productivity and quality. Remember that thorough evaluation and selection of the right tool will require funding, but this vetting must stay within your organization’s budget. Careful selection of the appropriate version control tool will help your firm improve productivity and quality and ensure that you are adhering to industry standards regarding configuration management best practices. About the Author Mike Feighner has more than twenty years’ experience in information technology in the aerospace industry, including more than ten years in configuration management. Mike graduated from San Jose State University with a bachelor’s degree in German and has a master’s degree in political science from the University of Tübingen in Germany and a master’s degree in software engineering from National University.

Tagged : / / / / / / / / / / / / / / /

IBM Rational ClearCase Version 7.1.1 release | Rational ClearCase New Version

ibm-rational-clearcase
ibm-rational-clearcase


IBM Rational ClearCase Version 7.1.1 release

This information provides a brief description of the new features and restrictions in IBM Rational® ClearCase® Version 7.1.1
What’s New

For a list of new features available in this release, see What’s New
Announcement
The Rational ClearCase Version 7.1.1 announcement is available at www.ibm.com/common/ssi/index.wss. See the announcement for the following information:

Detailed product description, including a description of new functions
Product-positioning statement
Packaging and ordering details
International compatibility information

System requirements

For information about hardware and software compatibility, see the detailed system requirements document at http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg21302974 .
Installing Rational ClearCase Version 7.1.1
For installation instructions, see this topic in the information center:

http://publib.boulder.ibm.com/infocenter/cchelp/v7r1m0/index.jsp?topic=/com.ibm.rational.clearcase.cc_ms_install.doc/topics/c_deploy_container.htm

Known problems

Known problems are recorded in individual documents in the Support knowledge base. As problems are discovered and resolved, the knowledge base is updated and maintained with new information. By searching the knowledge base, you can quickly find workarounds or solutions to problems. To learn about the known limitations and problems in this update, and any workarounds that are available, see: http://www.ibm.com/support/search.wss?&q=clearcase+RN7.1.1.
iFixes and Fixpacks
To learn about features and fixed defect fixes in Fixpack and iFixes:

Go to http://www.ibm.com
Click Support & downloads
In the Select product or service type for support box, select the software category and then the product category.
Under Choose your task on the left side, click Downloads.
In the Featured download links box, click View all download links.
Click the link for an iFix or Fixpack.

Source: Click here

Tagged : / / / / / / / / / / / / / / / / /

Perforce New Version , Perforce 2011.1 released | Perforce 2011.1 Overview

perforce-20111-version

Perforce 2011.1 released 11/07/2011

Perforce Release 2011.1 is now available. Check for platform and component availability.

Source: http://www.perforce.com/aggregator/sources/2

Tagged : / / / / / / / / / / / / / / / /

Stable CVS Version 1.11.23 Released, What’s new in Perforce CVS 2011.1, let’s find?

stable-cvs-version-1.11.23

Stable CVS 1.11.23 has been released. Stable releases contain only bug fixes from previous versions of CVS. This version includes an efficiency fix that reduces checkouts of very old revisions from an O(n^2) operation to an O(n) one, as well as yet another Windows file time stamp handling fix (bug #22781), and some other minor fixes and efficiency improvements. We recommend this upgrade for all CVS clients and servers!

Please take a look at the NEWS file from the CVS source distribution and the CVS 1.11.23 manual for more information about the changes contained in this release.

CVS can be downloaded from the GNU download server within four hours of this announcement or one of the mirrors after 24 hours or so (make sure to check the ”’non-gnu”’ directory on the mirrors). (This release may be obtained from Savannah download server prior to appearing on the GNU download server, but please don’t use the already heavily loaded Savannah download server unless you have to.) For other ways to obtain CVS, please read How to get GNU Software.

URL: http://savannah.nongnu.org/projects/cvs

Tagged : / / / / / / / / / / / / / / / / / / / /

Power Point PPT: Version Control With CVS – Complete Guide

version-control-with-cvs

Power Point PPT: Version Control With CVS

 

Tagged : / / / / / / / / / / / / / /

Apache Continuum Version 1.3.6 Beta 1 – What’s new in Apache Continuum ?

apache-continuum-version-136-beta-1

The Apache Continuum team have released a beta of Apache Continuum 1.3.6.

Apache Continuum is a continuous integration server, which offers automated builds, role-based security, release management and integration with build tools and source control management systems. The project aims to improve quality and maintain a consistent build environment.

This beta introduces updates to the error handling if deleting a project fails, and has fixed the invalid links when generating pdf of continuum-docs. Untested platforms have been removed from the installation docs, and the LDAP configuration documentation has been updated.

A PDF version of the Continuum docs is planned for some point in the future. See the Release Notes for more information.

Tagged : / / / / / / / / / / / / / / / / /