How to install latest allure 1 version?
Since release of allure 2, references to allure 1 binaries were removed from all sources. It seem to be not possible to install allure 1 via HomeBrew.
Allure 2 is great, however some plugins are not yet compatible with it. It would be nice to have a convenient way to install allure 1 for a time being.
You can download Allure 1 releases from Github https://github.com/allure-framework/allure1/releases/tag/allure-core-1.5.2
Related
For my project, I need .NET Core 2.2. The Chocolatey package repository states that .NET Core 2.2.8 is the most recent version of .NET Core 2.2 available. I can install this package with choco install dotnetcore --version 2.2.8 -m. But when 2.2.9 will be released, I will still be on 2.2.8, because I specified that specific version. What command do I need to have .NET Core 2.2 updated to a new minor version when I issue choco upgrade all?
EDIT: I do not want to upgrade to .NET Core 3.x when I issue choco upgrade all, because I have some projects that depend on it. Instead, I explicitly want Chocolatey to upgrade to .NET Core 2.2.9 if it will be released
While I think this belongs better on Super User, based on what is implied by using side by side installations of a package, if you want a new version of that package, use choco install -m to install the newer version of that package. Based on your experience of choco upgrade all upgrading one of your side by side packages however, you may want to inquire on the Chocolatey issue tracker as to what the recommended method of upgrading your other packages would be here.
I am attempting to use the latest angular2 quickstart files with a new empty ASP.NET Core 1.0 Web Application.
VS2015 Update 2 - w/ Core 1.0 RC2 installed
Steps to reproduce:
Create a new project using ASP.NET Core Web Application (.NET Core) - Empty Template
Add the 4 angular quick-start files to your root directory, NOT Hitting save on package.json until the other 3 are added and saved.
Finally, hit save on package.json and npm will start installing all of the packages. However, at the end I see Dependencies - not installed, npm - not installed. I can't figure out what could be causing this. It has to be a VS2015 / npm bug because if I use VSCode and npm from command line everything installs perfectly with this package.json file.
This is a bug in the Web Tools for ASP.NET Core RC2, which was discovered after RC2 was shipped. It's only that the "- not installed" UI is showing up incorrectly. The packages are successfully installed.
I'm not sure what is causing it yet, but we are aware of the issue and will try to fix this in a future release of the Web Tools.
I'm currently working in a work environment where I do not have access to npm / node. The npm download location is actually blocked so I can't get any packages.
I want to build an Angular 2 site. As I can't access npm, I want to use Nuget to get the files. Although I can see the Angular 1 packages, I cannot seem to see any Angular 2 packages. Is there one for Nuget?
Also, is populating the node_module folder and compiling the Typescript the only thing that npm does for Angular? If I can just get a copy of the node_module folder (from outside work) and get TypeScript working in my solution, can I basically bypass the need for npm?
In short; No.
You can see a list of all available NuGet package versions here, with the most recent being 1.5.3.
Even performing a generic search shows most recent versions as 1.5.3.
Sometimes they'll have beta versions of packages available that you can install with a command similar to: Install-Package EntityFramework -Version 6.1.3-beta1 -Pre, but it doesn't appear as if they have created any pre-release packages.
So, as #Michal Dymel mentioned, you could get it from a CDN or some other location.
I am running Jbehave tests and wanted to view the Jbehave reports on Jenkins. I have installed xunit plugin on Jenkins as mentioned in http://jbehave.org/reference/stable/hudson-plugin.html . When I configure xunit test reports under the Post-build Actions of Jenkins job, I do not see the option for JBehave to add the report. xunit plugin installed is v 1.61. Can anyone tell me if I m doing something wrong or missing anything here?
Ok so to see your jbehave tests in jenkins you need install on jenkins
xUnit jenkins plugin
Then install JBehave Hudson Plugin
2.2 Read about it here
http://jbehave.org/reference/stable/hudson-plugin.html
2.3 Download hpi file (I use:
jbehave-jenkins-plugin-3.7.4.hpi Sat Nov 24 04:38:22 CST 2012 90030
) from:
https://nexus.codehaus.org/content/repositories/releases/org/jbehave/jbehave-jenkins-plugin/3.7.4/
2.4 Go to your jenkins to pluginManager/advanced and in sectionUpload Plugin ad downloaded file and upload it
2.5 It should become visible in pluginManager/available section - so just check and install it.
Now navigate to your build to xUnit Post-build Actions and enjoy jbehave options
3.1 Add directory where plugin should look for xml report like **/jbehave/*.xml
3.2 If your jbehave is configured properly you should get all reports located in your workspace
If you need more help like configuring html view of jbehave reports, setting maven etc. make new question or update this one
Cheers
You may not have to use xunit plugin to see the test reports.
There are other options available.
Make sure you have generate the required outputs (org.jbehave.core.reporters.XmlOutput). Then just publish the Junit test result.
Make sure you have generate the required outputs (HTML). Include
<dependency>
<groupId>org.jbehave.site</groupId>
<artifactId>jbehave-site-resources</artifactId>
<version>3.1.1</version>
<type>zip</type>
</dependency>
And you can publish as one of the HTML reports.
I have installed beta package on test org. Now i have released another beta package.
But while installing it in test org it is now allowing to install.
So, Can we install Beta version on existing beta package?
Thanks in advance.
If it is an upgrade to an existing managed package you must first uninstall the current version.